Best upgrade path 11.2.0.2 to 12 ° c

Similar Questions

• C / SX / EX / MX upgrade paths

  Hello

  I have been the scene of c20 upgrades via the GUI and CPC, 4.x > 5.1.1 > > 7.3.2 7.1.1 hopping. 3rd party support told me that this is the way to upgrade the C20s.

  I struggled to find any documentation to confirm this upgrade path to 7.3.2. I'm about to proceed to the upgrade C40s and 60 with SX / EX / models MX.

  I'm looking for the validation of the document confirm how best to spend to 7.3.2 on all of the above models.

  I looked at the release notes do not seem to talk about any version of jump requirement.

  Thank you

  B

  You can go directly to the current version of the TC software without having to jump several releases to get there.  You'll just need to get the keys to unlocking the Cisco Licensing Portal TC7.x and apply it on the codecs, before doing the upgrade.  Applying the unlock key invites you to restart, you can disregard and go directly to download TC as the upgrade to restart anyway endpoint and apply the release key at the same time.

  Note, it is important that you read well ALL the TC release notes for the current version, you have up to TC7.  There are several versions where changes have been made that could be important to you.  Some of these changes are:

  • TC5.x - required serial connection is by default enabled (important only if you use control 3rd party such as Crestron or AMX systems)
  • TC6.x - layouts have changed, especially when using two screens with presentation and selfview.
  • TC7.x - Root access has been removed (I noticed that mention you SCP that requires root access), also instantaneous behavior has changed over the previous day.

• Impossible to reinstall XP, error «...» Windows is not a supported upgrade path"

  Computer is 2001 Sony Vaio apparently infected Office who knows what, if I want to do a clean install of the operating system. The computer came with Windows ME and a drive to upgrade to XP. 5 years, a technician thought he was doing me a favor and installed without my knowledge its own XP Pro.

  I tried to do an installation of my upgrade XP disc but I get this message: Setup is impossible to pass your current installation of Windows XP. Your current Windows installation is not a supported upgrade path. Setup cannot continue.

  I also tried to use the Sony system recovery CD, but it does not work.

  Help!

  Hi IAMSOBZ,

  As you install the operating system from a CD to upgrade it you will be asked for support of qualification, you can insert your Windows Millennium Edition or any CD which is an edition less than Windows XP Professional.

  Important: You will need to have a CD of Windows 98/Me/2000 eligible to insert if you are using a version update of XP to clean install. OEM restore disks will not usually fill the eligibility standard. If the restore disc i386 folder, it will work normally.

  a. start your computer from the Windows XP CD-ROM. To do this, insert the Windows XP CD into your CD or DVD and then reboot your computer.

   

  Note: To boot from the Windows XP CD, your computer BIOS settings must be configured to do this.

  b. When you see the message "Press any key to boot from CD", press any key to start the computer from the Windows XP CD.

  c. once the Welcome to Setup screen, press ENTER to start Windows XP Setup.

  d. read the Microsoft software license agreement and press F8.

  e. Setup will scan for previous Windows installations

  f. you will need to replace the CD of XP with your qualifying CD; XP Setup will scan the qualifying CD and ask you to replace it with the XP CD to continue installing XP.

  g. complete the installation

  You can refer the link to find out how to install Windows XP below: how to install or upgrade to Windows XP: http://support.microsoft.com/kb/978307

  With regard to:

  Samhrutha G S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• IDRAC6 upgrade path

  I am temporarily caring for a Dell PowerEdge T610 purchased in 2012.  Our outsourced IT Department walked me through some maintenance tasks, including required launches a Virtual Console through iDRAC6. Apparently my iDRAC6 version (V1.80) is so old, no modern browser it supports fully. What I have for the most part works with Chrome and FireFox, not IE (but it's OK - I don't work with IE either).

  I am trying to determine if a firmware upgrade path exists for my hardware, and if so, what are the steps. None of my research on the Dell Web site have meaningful results. Since my system is no longer under warranty I don't get a lot of help by telephone, and "cat" is denied for me as well.

  If anyone can point me to a good place to get started which would be a great help.  Thank you!

  Hello.

  See the upgrade below. First apply the BIOS, then the respective DRAC6 firmware.

  6.2.3 BIOS iDRAC6 v1.92                   

  BIOS 6.3.0 iDRAC6 v1.95                  

  BIOS 6.4.0 iDRAC6 v1.97, iDRAC6 v1.99 , and iDRAC6 v2.8.0                  

  The path of update will prevent iDRAC communication and other server issues.

• Upgrade path 5500 series ASA-SSM-10

  Can anyone provide the proper for the 5500 series ASA-SSM-10 upgrade path of

  6.0 (5) E2

  TO

  7.1 (10) E4

  The release notes state that you must run just least 6,0000 e4 could so I just spend 6,0000 E4 5,0000 E2 then directly to 7.1 (10) E4?

  Also, the SSM-10 is able to effectively run the 7.1 (10) E4?

  Hello

  Yes, you can directly upgrade 6.0.5E2 to 6.0.6 E4 and then directly to version 7.1. (10) E4. After the upgrade for the latter, you might even go to latest available patch as well.

  -Yes, SSM1 - is able to effectively execute the 7.1.0E4.

  Kind regards

  Akshay Rouanet

• ACS 5.1 upgrade path

  Hello

  I have just unpacked ACS1121 with 5.1.0.44... Version of the ACS software. Y at - it (upgrade path) proceedings at this level to a version 5.2.x (later

  5-2-0-26-5)?

  You use a repository of tftp. If so try with a ftp repository

• 13.2.2 to 14.5.0 TMS upgrade path

  Hello

  I'm looking to make an upgrade to TMS 13.2.2 we currently have running on an old box of Windows 2003 R2.

  We are looking to set up a new server using 2012 R2 as the operating system.

  The environment:

  Windows 2003 R2

  SQL Express 2005 w/DB hosted locally

  13.2.2 TMS

  TMSXE (on another server) 3.0.2

  The methodology of Migration:

  Migrate the existing database to a SQL server hosted and test all the features

  If it is successful then

  • Remove the old server from domain/network
  • Rename the new server the same as
  • Install the TMS 14.3.0 on the new connection to the existing database server, hosted on the external SQL Server
  • Run the time zone update tool that comes in 14.3.0
  • Update the 14.3.0 existing install 14.5.0

  This methodology seems as if it was the right way to go? There are fundamental flaws, that I don't see here?

  I did this upgrade path in the laboratory successfully using a copy of our existing database, I have no alternative endpoints or vcs-control etc. to connect to the lab to prove everything works after upgrade.

  I look forward to your responses.

  Thank you

  Alex

  Hello Alex.

  You should consider upgrading to TMS 14.6, which is the most recent version.  14.6 TMS notes.

  TMS 14.5 supports only Windows Server 2012, not 2012 R2, but 14.6 done TMS.  Also, if you are not already the case, consider using SQL Server 2012 or 2008 R2 64 bit, to be compatible with future versions of TMS.

  The steps that you listed sounds good, just check on that TMS installation guides for supported versions of WIndows and SQL details, as well as all the required components.

• vCD 8 upgrade path

  Hi all

  Can upgrade you form vCD 5.5 directly to vCD8.0 or are you to go first to 5.6.4?  I can't find anything in the notes version or installation & Upgrade guide.

  Dave

  OK - I answered my own question with the Matrices of the interoperability of VMware products.  I don't know if the "Upgrade Path" option is new, but I don't remember having seen it before.  In any case, the vCD 8.0 upgrade is supported from version 5.5.4 and 5.6.4.

  Dave

• Where to buy the best upgrade of ram for Mac Pro end of 2013

  Where do you want to buy the best upgrade of ram for Mac Pro end 2013.  I am under creative cloud.  Thank you!

  It is a software Adobe forum... you need to find a forum for Mac hardware

• Upgrade paths for vCenter Server 4.0/32-bit to 64-bit/5.0

  So, for various reasons beyond my control, when we installed vCenter server when we migrated from 3.5 to 4.0, it has been installed on 32-bit Windows.

  Data backended by a full instance of SQL Server (not the MSDE version that comes pre-packaged with vCenter).

  So, I try to understand the strategy of less impact for the trip to 5.0.

  One idea I had is simply to build a new 'home' for vCenter Server on x 86-64 and point the application on the existing database running on 32-bit windows server. (I'm guessing that the 32/64-bit nature of the database server itself is largely irrelevant as it allows 64-bit vCenter Server to talk to it). I think then that all information cluster all would remain intact since it's in the database, etc..

  If I had to, I guess, we could install vCenter 4.0 (64-bit) on the new host and THEN perform the upgrade, if it was really important, but I somehow don't think it is.

  Once that is done, we would eventually just make a backup/restore type upgrade path to move data out of the old host and the new host and re-point vCenter Server in its local database now.

  A that someone does something similar to this? Traps, we should be aware of? Warnings that it would never work the way we expect it to be, etc, etc. ?

  One idea I had is simply to build a new 'home' for vCenter Server on x 86-64 and point the application on the existing database running on 32-bit windows server. (I'm guessing that the 32/64-bit nature of the database server itself is largely irrelevant as it allows 64-bit vCenter Server to talk to it). I think then that all information cluster all would remain intact since it's in the database, etc..

  That's what I'd do.  It your DB is remote, it is a fairly straightforward upgrade.

  1. turn off your old Instance vCenter

  2. backup your DB instance

  3 copy the SSL directory off the old vCenter and the new (you'll probably to manually create the path, before installing vCenter)

  4 set up your ODBC connection and test

  5. install vCenter and use existing DB

  Assuming that you are going to use the same host name and IP address for your new instance of vCenter, like your old, all stocks will be as it was before the upgrade.

• Adobe Reader 8.1.7 upgrade path?

  Could someone please explain the upgrade path to Adobe Reader 8.1.7 for me? I read the tech note "Adobe Acrobat and Reader to date and deployment information" and I am still a little uncertain.

  Our most currently deployed version is 8.1.6 but some of our users still have older versions (8.1.2 ~ 8.1.5) installed. I've been distributing Adobe Reader via SMS 2003 from version 8.1.2 as below:

  8.1.2 - customized using Adobe Cusomtization 8 (Setup.exe /sPB /rps /rs) Assistant

  8.1.3 - customized using Adobe Cusomtization 8 (Setup.exe /sPB /rps /rs) Assistant

  8.1.4 - straight (number installAdbeRdrUpd814_all_incr.msp! /norestart)

  8.1.5 - right installation (number AdbeRdrUpd815_all_incr.msp! /norestart)

  8.1.6 - right installation (number AdbeRdrUpd816_all_incr.msp! /norestart)

  So, what is my upgrade for Adobe Reader 8.1.7 - right installation path (number AdbeRdrUpd817_all_incr.msp! /norestart) or do I need to customize using Adobe's Assistant to keep the desired settings? Appreciate any advice anyone can offer. Thank you very much.

  Adobe Reader 8.1.7 patch can be applied only to 8.1.6. Then first you must bring all your systems to 8.1.6 and then apply 8.1.7 patch.

  Custom settings do not download if you install 8.1.7.

  If you have a system with 8.1.3 or 8.1.4 or 8.1.5 so that-

  Apply 8.1.6 patch--> Apply 8.1.7 patch

  If you have a system with 8.1.6 then do-

  Apply 8.1.7 patch

  If you have a clean system, then the shortest is to install the reader 8.1.7-

  Install Reader 8.1.6 Apply patch 8.1.3-->--> Apply 8.1.7 patch

  NOTE: Reader 8.1.3 is an install (msi) full 8.1.6 and 8.1.7 are patches (msp).

• Best practices Upgrade Path - Server 3 to 5?

  Hello

  I am trying a migration and upgrade of a server in the Profile Manager. I currently run an older mac mini Server 10.9.5 and Server 3 with a vast installation of Profile Manager. I recently successfully migrated the server itself out of the old mac mini on a Xserve end 2009 of cloning the drive. Still of double controls everything, but it seems that the transition between the mini and the Xserve was successful and everything works as it should (just with improved performance).

  My main question is now that I want to get this software-wise at day and pass to the Server 5 and 10.11. I see a lot of documentation (still officially Apple) best practices for the upgrade of the Server 3 to 4 and Yosemite, but can't find much on the Server 5 and El captain, a fortiori from 3 to 5. I understand that I'll probably have to buy.app even once and that's fine... but should I be this staging with 10.9 to 10.10 and Server 4... Make sure that all is well... and the jump off 10.11 and Server 5... Or is it 'safe' (or ok) to jump 3 to 5 Server (and 10.9.5 to 10.11.x)? Obviously, the AppStore is pleased to make the jump from 10.9 to 10.11, but once again, looking for best practices here.

  I will of course ensure that all backups are up-to-date and make another clone just before any which way that take... but I was wondering if someone has made the leap from 3-5... and had things (like the Profile Manager) still work correctly on the other side?

  Thanks for any info and/or management.

  In your post I keep the Mini running Server 3, El Capitan and Server 5 install the Xserve and walk through setting up Server 5 by hand. Things that need to be 'migrated' as Open directory must be handled by exporting the mini and reimport on Xserve.

  According to my experience, OS X Server facilities that were "migrated" always seem to end up with esoteric problems that are difficult to correct, and it's easier to adopt the procedure above that to lose one day try.

  YMMV

  C.

• PS6500e Firmware 4.2 upgrade path and best practices

  recently took on the administration of a PS6500E 1 42 to disks, M1000, PC6224, these units have sat unused for several years. ~ 5-8, I don't think that it was already in use!  Time was limited to undertake this task, however, I have downloaded and read even if a lot of documentation in time allows. .

  Small steps to check the functionality of the hardware has been my first priority.

  Presentation of SIMPLE material:

  > PE R710

  > PS6500E

  > PC6224

  > M1000 w / 16 blades

  < start="" testing="">

  --> create an account on the Eql support site

  --> created an account here!

  --> Documented the original wiring of config, the topology of the network.

  --> All the firmware documented on all units (do not have on hand that I write this aaarg!)

  --> re-cable, stripping everything and restart in a topology to know. (KISS)

  --> Rebuilt R710 head with RHEL-6, 8.

  --> Rebuilt all the blades (16) with RHEL-6, 8

  --> creates user accounts for the test on all systems

  --> installed required use SW for development

  --> Explained to the users it is the trial step ONLY

  --> Users started to test the functionality (adding more requirements on the way!)

  --> Explained to the users it is the trial step ONLY. Laughing out loud

  --> Functionality tests, users (adding more requirements, you get the picture I'm sure)

  --> has added 144G RAM to the head node. 8G (original)

  --> Added 8 TB USB disk storage of data (user does it... äarg!)

  --> Sharing NFS (8 TB USB) to head-node BS1-16 (more added requirements)

  --> Test user account created on the NFS share/users/home and accessible across all systems

  At this point, I need to get the PS6500E ant online tested before this monster grow out of control.

  I was able to access the unit via a serial connection resetting the grpadmin password and run the installation through the command line.

  Now I have access to the GUI and performed the tests at the point of creation and connection to a new volume via iSCSI for the head node.

  --> Presentation of networks of config:

  --> MGMT == 192.168.1.0/24 (IPMI / Dell mgmt?) CMC

  --> Calculation == 192.168.2.0/24 Comm. head-node network and 16 blades

  --> PS6500 / R710 iSCSI == Comm. head-node 10.0.50.0/24 network and PS6500E

  --> PC6224 == do not have access to this device again.  Looks like a flat configured swx

  --> X 2 and 2 x CMC M1000 SWX modules modules connected between them and 1 cable for the PC6224

  --> KVM interconnection works to all nodes (never use however)

  What is the best way to get the firmware on this day and the current version.  I'm not worried about the loss of data at this stage.  Don't forget that we are TESTING!

  Thank you for taking the time and I appreciate any help, advice, comments.

  Hello

  Since it has not been used, I suspect it is no longer under contract?   The service contract is what keeps your license for the software and firmware that Dell is in charge of the PS Series SAN associated.

  If you will not be able to update the firmware, if that's the case.  If it's somehow, then you download the firmware on the site eqlsupport.dell.com, login required.  The upgrade would take action a bit.  4.2.x->->->-> 7 6.0.x 5.2.x 5.0.10.. 1.x-> 8.1.x-> 9.0, which is common.   There is a firmware u; Guide with each version of firmware that includes a table with this in grade.

  Note, firmware update requires not never delete data or resetting the table.

  Once that access you the switch, you'll want to level it as well.  Many patches associated with iSCSI for the switch.

• ESXi 3.5 to 4, issue of... new installation or upgrade path?

  Hello

  I have a test ESXi 3.5 server that contains 3 VM.  It's all local storage.  I don't have a vCenter.

  What is the best way to upgrade?

  (1) perform a real upgrade to theVMware ESXi 4.0 (upgrade ZIP) and VMware vSphere Host Update Utility and customer.

  (2) perform a clean installation of ESXi 4.

  I would prefer to use (2), but first: a clean install of will wipe away the existing VMFS partition where the virtual machine of resident?

  Thank you!

  A new installation will wipe existing VMFS data warehouses so you'll want to take the path of upgrading.  http://www.vm-help.com/esx40i/ESXi40_upgrade_without_virtualcenter.php - Note that you should be able to get a direct download to the client vSphere instead of having to extract, upgrade the upgrade zip file.

  Dave

  VMware communities user moderator

  New book in town - Start Guide quick vSphere -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

  You have a system or a PCI with VMDirectPath?  Submit your specifications to the unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.

• Question about the upgrade path Essbase

  Hi Techies,
  
  We are modernizing Essbase in windows since version 7.1.6 to 9.3.1 platform. Now my question is what is the best way to do that, as first upgrading to 9.2 then 9.3.1 or completely uninstall and reinstall the version 9.3.1 directly? In Essbase 9.3.1 application is rebuilt from scratch, so we thought to stick with the second option IE 7.1.6 to uninstall and reinstall 9.3.1. But now we have other applications that must be replicated from 7.1.6 to 9.3.1 an app frame. We heard that we must follow the path of upgrade first to 9.2, then in 9.3.1. Is this true? !!
  
  Can you guys shed some light on this as well as the consequences of each option, if applicable.
  
  Thanks in advance
  
  K

  personally, I would be completely uninstall, make sure that all the elements of the old version have disappeared, so check the registry and environment variables have been removed. Then install the 9.3.1.
  As it seems as you are going to use the same server, then for the applications that you want to migrate upward all objects (outlines, scripts of calc, rules, reports), export the data.
  So if you want to export security and filters, then I would look using the essbase (free utility) Advanced Security Manager. Then rebuild the applications once the new environment has been built.

  See you soon

  John
  http://John-Goodwin.blogspot.com/