Windows 10 Domain Issue
-
I updated it on Friday before I made my new base image. After making the image I went to Service Configuration and downloaded/installed the FOG Client from there. I was assuming that was the most up to date version.
I just checked and I appear to be out of date now, but I’m running the following.
Running Version 1.3.0-RC-1
SVN Revision: 5936 -
@Towndrunk But if you updated, why is your client still using the legacy client?
While it is true the “new client” does autoupdate, that’s only if the new client is installed on the image. If you have the old fog client installed, you are not working with the new client.
-
-
I just ran the update, and then downloaded the client again to install. When I tried to install it, I received a message telling me to “Please uninstall the legacy client and re-run this installer”. I went to Programs and Features and uninstalled the FOG Service, and rebooted. When I go back in and try to run the install I get the same message.
Running Version 1.3.0-RC-2
SVN Revision: 5937 -
-
@Tom-Elliott Thanks, I found that while I was searching after I posted. I don’t have any Keys starting with 91C5D423 in that location. I was thinking the same thing, searing the registry to remove anything related to FOG Service, but I wanted to see if I was missing something first.
Is it possible that it is another entry in that same location?
-
@Towndrunk that is the exact registry key the new client uses to detect a legacy installation. If the installer reports that the legacy client is still on your system than that registry key must exist.(make sure to include the curly brace in your search). If it still doesn’t show then search the whole registry for that exact key, and if you could report your findings.
It may be in a different root folder, but the path will always contain
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstalland be in the local machine root section. -
@Joe-Schmitt thanks for the response. I did a search for it and found it in another directory. The directory below is where I found it, not sure how you make it red like yours. I removed it and was able to install the new client. I’m going to do another capture and see if I get a different response.
HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
-
Thanks so much for the help. I would not have figured that out without your help. Once I remove the old client, updated to the new, and ran a new capture. . . I’m able to deploy with no issues now. It is adding to the domain as we had hoped now.
-
@Towndrunk said in Windows 10 Domain Issue:
I imaged a computer that was activated and on the domain. After applying that imaged to another computer it says that is on the domain when I log in locally, however there is no trust relationship.
If your image is already joined to the domain, you will have nothing but problems, and major ones at that. There is no imaging solution made by anyone that would suggest taking an image from a domain-bound computer. They all suggest exactly the opposite, take an image of an un-bound system.
