Basically after you have finished a shadow protect recovery, before booting into the operating system it is recommended that you boot into certain modes for certain server roles (eg: for a domain controller, boot into active directory restore mode, for SQL servers.. safe mode with networking).
When I did this, I was unable to install the Microsoft Integration Services setup as I would get the following error half way through the installation:
An error has occurred: One of the update processes returned error code 1601
Now, this puts you into a bit of a quandary as you shouldn't boot certain servers with certain network roles on them without a network adapter installed.
To resolve this issue (make sure you have ran the installation first), I used keyboard shortcuts to get into the Integration Services setup CD and copied the files sitting under the following .cab files to a location on the C:\ drive (only grab either x32 or x64)
Windows6.0-HyperVIntegrationServices-x64.cab
Windows6.0-HyperVIntegrationServices-x32.cab
Once this was done, I went into device manager and manually installed the missing drivers.
Once completed, I was able to access mouse capabilities but I still couldn't get into the network card (even though it was installed). After another reboot (and back into the certain safe mode), I was able to set the IP of
the network card and remove the hidden devices.
Once I was in the operating system (not safe mode), I was able to do a repair install of the Integration Services without any issues (did loose network connectivity for around 20 seconds during the process).
I then went onto recover some Windows 2008 R2 servers and noted that they didn't not have the problem mentioned above.
thanks you saved my time
ReplyDeleteDude, I was thinking of doing that, having a very similar error, but I thought it wasn't worth trying. I am so glad you blogged this. Saved my butt! Physical server went down hard, no coming back. I had made vhds of every server for just in case this happened. Pretty good backup strategy actually :)
ReplyDeleteThanks for this, it allowed me to get Integration Services installed on an old XP box. This was for Hyper-V on Server 2012 R2 and I extracted the 6.2 cab and used the files to install loads of drivers.
ReplyDeleteCheers for that mate, good to hear it still works for Win 2k12 R2!
DeleteExtremely helpful, thanks for sharing this. I had the same error after virtualising an ancient Windows XP physical machine. Following your method I was able to get the damn mouse working!
ReplyDeleteThanks for giving me another troubleshooting path. I tried the instructions above and was able to manually fix the two unknown devices in the device manager that I thought were holding it up, but in the end I just removed the original version of Integration Services, rebooted, then it reinstalled without issue.
ReplyDeleteSites like yours are an asset to the 'net.