Y Y
asked on
Accidentally installed 32 bit Integration Services on a 64 bit guest. Now what?
The host is Win2012 STD with Hyper-V role enabled, the guest is SBS2011.
The "Integration Services" is on the guest's D: drive. It has two folders: x86 and AMD64.
I mistakenly ran setup from x86 folder on the guest. Then I realized that I should have run setup from AMD64 folder. Trying to correct this, I ran setup from AMD64 folder, but a message popped up saying that I was already on the latest version and it would not continue.
Well, the guest seems to be okay so far even with this mistake.
How should I correct this mistake if it matters?
Thanks!
-
The "Integration Services" is on the guest's D: drive. It has two folders: x86 and AMD64.
I mistakenly ran setup from x86 folder on the guest. Then I realized that I should have run setup from AMD64 folder. Trying to correct this, I ran setup from AMD64 folder, but a message popped up saying that I was already on the latest version and it would not continue.
Well, the guest seems to be okay so far even with this mistake.
How should I correct this mistake if it matters?
Thanks!
-
ASKER
That is the first place I have ever looked, but it's not there at all. So it cant be uninstalled easily
Look in Control Panel, Programs and Features and then Windows Features (left side). Is in Windows Features? If so, uncheck it, restart the Server and then install it again.
ASKER
Will let you know in 2 hrs
ASKER
no, not there as expected.
If the guest machine is running properly, you may consider leaving it.
There is a repair for Windows 8 / modern servers that you can consider running called DISM.
Open cmd.exe with Run as Administrator.
DISM.exe /Online /Cleanup-Image /Scanhealth (takes 15 - 20 minutes).
DISM.exe /Online /Cleanup-Image /Restorehealth (takes 15 - 20 minutes).
Restart the computer and test
I don't know if this will change anything, but you could see if ScanHealth produces anything.
It may be that installing from either location installed the correct version for the Server, so really, the Server may be fine.
There is a repair for Windows 8 / modern servers that you can consider running called DISM.
Open cmd.exe with Run as Administrator.
DISM.exe /Online /Cleanup-Image /Scanhealth (takes 15 - 20 minutes).
DISM.exe /Online /Cleanup-Image /Restorehealth (takes 15 - 20 minutes).
Restart the computer and test
I don't know if this will change anything, but you could see if ScanHealth produces anything.
It may be that installing from either location installed the correct version for the Server, so really, the Server may be fine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Very helpful.
Good to know some new OS already have Integration Services included. Yes, it is weird that I got 32bit installed on 64bit successfully.
I have checked vdu driver, it does not have anything like amd64. See attachment. I also check nic driver, same thing.
VduDriver.png
Good to know some new OS already have Integration Services included. Yes, it is weird that I got 32bit installed on 64bit successfully.
I have checked vdu driver, it does not have anything like amd64. See attachment. I also check nic driver, same thing.
VduDriver.png
You need to click on the "Details" tab, then in the "properties" dropdown, select "Driver Node Strong Name", the amd64 is shown there under "value". At least that is so in my Windows 7 VM running under Hyper-V.
ASKER
Okay got it. and saw the keyword amd64. Thanks!
If the 32-bit is OK and does what you want, you may not need to change it at all.