Got it thanks. Trying to trouble shoot AD not working. We never had a AD before, we were eDir. The machines manually join or will join with power shell. Thanks. so now I know when it renames it should join. Will help with my trouble shooting.

Thank you so much for all your assistance!!!
FOG is fully functional again.

You guys are the best!!!

Did you ever try [SHIFT] + [SHUTDOWN] ?

@Tom-Elliott Just tested it and its working fine again now. Thanks!

@cojohnson You have a very unique troubleshooting style.

@Tom-Elliott @ChrisRaff That usually depends on the contents of the unattend file (assuming one is being used). Using the Fog client for domain joins would probably resolve this issue, assuming there is a group policy in place to disable the firewall or modify settings so that your remote management software would be able to connect.

Thanks Tom,

I don’t find any product key staying in my unattend.xml file (the one in c:\windows\system32\sysprep)

Do you think the product key used for activating the Windows image can be the problem?

<?xml version="1.0" encoding="utf-8"?> <!--This answer file generated by RT Seven Lite--> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>fr-FR</UILanguage> </SetupUILanguage> <InputLocale>040c:0000040c</InputLocale> <UserLocale>fr-FR</UserLocale> <UILanguage>fr-FR</UILanguage> <SystemLocale>fr-FR</SystemLocale> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <value>Windows 7 PROFESSIONAL</value> </MetaData> </InstallFrom> <InstallToAvailablePartition>false</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> <UserData> <Organization>Courcouronnes</Organization> <FullName>Courcouronnes</FullName> <AcceptEula>true</AcceptEula> </UserData> <UseConfigurationSet>true</UseConfigurationSet> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Name>admin</Name> <Group>Administrators</Group> <Password> <PlainText>false</PlainText> <Value>bgBiAGEAMQAyADMAUABhAHMAcwB3AG8AcgBkAA==</Value> </Password> </LocalAccount> </LocalAccounts> <AdministratorPassword> <Value>cwBlAGMAdQBhAGQAbQBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> <AutoLogon> <Password> <Value>cwBlAGMAdQBhAGQAbQBQAGEAcwBzAHcAbwByAGQA</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>5</LogonCount> <Username>Administrator</Username> </AutoLogon> <OOBE> <NetworkLocation>Work</NetworkLocation> <HideEULAPage>true</HideEULAPage> <ProtectYourPC>1</ProtectYourPC> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <TimeZone>Romance Standard Time</TimeZone> <OEMInformation> <Manufacturer>SI</Manufacturer> <SupportHours>L:J 8h15-17h30 V:8h15-15h30</SupportHours> <SupportPhone>XXXXXXXX</SupportPhone> <SupportURL>https://obsidienne.courcouronnes.fr/glpi</SupportURL> <Model>1337</Model> <Logo>%systemroot%\system32\OOBE\courcouronnes.bmp</Logo> </OEMInformation> <ShowWindowsLive>false</ShowWindowsLive> <RegisteredOrganization>Courcouronnes</RegisteredOrganization> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>RENOMMER</ComputerName> <CopyProfile>true</CopyProfile> </component> <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipRearm>1</SkipRearm> </component> <component name="Microsoft-Windows-Security-Licensing-SLC" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipRearm>1</SkipRearm> </component> </settings> <cpi:offlineImage cpi:source="wim:d:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

@Wayne-Workman Upgrade worked perfectly. Thanks again for your help. You can mark as solved.

Chris

@Tom-Elliott alright, cool.

Sorry for my ignorance, but I seem to remember Snapins before needing to be wrapped with SFXMaker and such for all things. Is that still the case, or can I now just upload a script and be done with it?

UPDATE

Never mind, uploaded a bat file and it ran flawlessly. Thanks for the help, now my thin imaging with PDQ to throw apps on afterwards is working fantastically across all sites!

I also wouldn’t call a RAW image a success. It’s more of a stalemate.

Thank you for the help, glad its not a FOG Issue. Will look into getting the dead hard drive replaced.

-swainy

@Junkhacker
Well this was the interesting bit, it was all physical, the MACs imaged up were those of the physical adapters, but Hyper-v was “moving” the physical MACs to it’s internal network cards, and then of course imaging the software MACs up. Interesting, a pain but quite interesting.

As I said everything works great! Thank you again for great support!

@Tom-Elliott Version 7007

If i save the username as test\test it works on the first pass. I am not sure if this changes anything but i was setting the user/password at the global level. and the group level I never set it at the host level. I would also get it to work once then image the system and after the image it would begin failing.

@GreenItSolutions Does the disk actually have an OS installed on it? What format is the system booting in? EFI, BIOS, some alternate config I’m completely unaware of?

@GreenItSolutions Great to hear that it’s working with a dump switch. Please let us know when you find the solution and explain it here for other people who might run into the same issue… Thanks in advance!

So this problem definitely relates to a windows xp to windows 10 file transfer issue and is nothing to do with fog.
From what I found here http://helpdeskgeek.com/office-tips/fix-office-2010-cannot-verify-license-error-message/
I discovered that the file tokens.dat is indeed a part of activation.
If you happen to have a similar problem…

stop the service osppsvc
Delete or rename tokens.dat and cache.dat found at C:\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform
Start the service osppsvc
Open any office program and let it do the self repair

This also fixes the problem of the office installer autoclosing when trying to repair or uninstall.

No worries with the trunk build either. I can say you will need the trunk build if you have newer hardware and/or you have to deal with gpt hard drives or uefi bios. All require the latest trunk version to work.

There are still being reports of bugs in the trunk build. Once reported they are fixed quite quickly. The point being you may need to update your fog server often until the developers get into the release candidate stage of deployment.

I can say from personal experience win10 with BIOS and MBR disks deploy without issue.

@Sebastian-Roth that registry key is perfectly fine. The reason it looks like it’s missing a backslash is because of a bug in the registry handler logging mechanism in pre-0.9.12. But even if it was missing that slash, that registry key will not affect anything of importance