@mikeakin44 Please read trough this topic: https://forums.fogproject.org/topic/13922/dell-optiplex-aio-5270

@Sebastian-Roth Well if they don’t match that may be part of the issue. The layout is from two identical Optiplex 7060 with 500GB drives. Top was one that imaged successfully, bottom is what I see when it doesn’t. All should match my golden image which is also an Optiplex 7060 with a 500 GB drive. I’m not sure where the disconnect would be from fogs settings, the image, and what ends up on the machine. Again I’ve more or less gotten around this by modifying my image. So I figure if this issue is unique to me it’s probably safe to let it go. If it does start poking up from others at least my info would be a good starting point.

@george1421 Sooooo as stupid as this sounds but I have a solution / workaround. Reduce the number of CPU’s on the VM to 1 Enable migrate to a physical computer with a different processor version Changing either of these setting causes the speed to bottom out at 21mb/m leaving the setting at this results in 230mb/m capture speed.

Hey, I downloaded the ISO file of Windows 10 Home from third party source and I am also stuck in proceeding further. Any help will be appreciated.Thanks in Advance.

This worked! Thanks! I’m disappointed Microsoft’s method doesn’t work anymore, it was super helpful when we were testing Windows 10 at my previous site…

@p4cm4n also, tried cmd and batch from sfx archives, specifically 7zip sfx maker which threw an error trying to run on my own machine and winrar sfx maker. Rar is crappier compression but oh well. One of those worked can’t remember which…but things like wifi configs using it didnt.

This feels much better! Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly. A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice

@lukebarone said in Windows 10 SysPrep not working: @loosus456 Yea, I have no objection to that. But I can’t get the Taskbar Customization to work (even after fixing the .xml file that is generated), so I gave that part up. It resets the taskbar to just Edge and Explorer, and allows users to customize it how they wish. Hi, you need to apply taskbar customs via group policy, if so the user has change rights: https://social.technet.microsoft.com/Forums/windows/en-US/83b725f4-90f8-476a-bba0-3193e4e47d2e/windows-10-1607-enterprise-taskbar-items-pinned-via-layoutmodificationxml-and?forum=win10itprosetup IMPORTANT If you use a provisioning package to configure the taskbar, your configuration will be reapplied each time the explorer.exe >process restarts. If your configuration pins an app and the user unpins that app, the user’s change will be overwritten the >next time the configuration is applied. To apply a taskbar configuration and allow users to make changes that will >persist, apply your configuration by using Group Policy. https://technet.microsoft.com/en-us/itpro/windows/manage/configure-windows-10-taskbar?f=255&MSPPError=-2147217396 What ever can be done by gpo should be done with gpo (ms philosopy). If you don’t have a domain controller for gpo applyment you can simply use gpedit.msc locally to set this on your golden image. Regards X23

I have tried many ways and it seems that powershell can’t do this or i missed something. What i have tried now is to make a snapin pack with psexec.exe and a batch file. Also in this batch i can’t write to HKCU. I used now the following code to store the key and this works for now. It’s not a nice solutions but it works. If anyone can give me the trick to do this in powershell, let me know. PsExec.exe -i -s -u %COMPUTERNAME%\%username% -p -nobanner -accepteula -i REG ADD "HKLM\SOFTWARE\Test" /v "Machinenummer" /t REG_SZ /d %COMPUTERNAME% /f

@Paulo-Guedes See update here: https://forums.fogproject.org/topic/11207/error-could-not-open-inode-xxxxxx-through-the-library

@espynn In such case, I’d recommend creating a fresh & clean image to try out next.

Just Kidding :))))) I just added the other architectures under the helpful little NOTE: and it works just great! I Skim too much and don’t read enough. You guys are great.

@Tom-Elliott thanks, we managed to push the image with our work around in time, I can try your fix out soon when we re image the machines

@Tom-Elliott from the logs: 10/7/2016 10:32 AM PowerManagement On demand shutdown requested. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button.

Depending on your hardware, you may need the right driver. Or if you’re in a VM, you need to select the right device to emulate.

This issue only appears to happen on windows 10 installations. It would seem the legacy client uninstaller is not fully compatible (of sorts) with windows 10.

@mcgill-eus if you follow the Upgrade to Trunk instructions exactly, you’ll get Release Candidate 6. RC-7 will probably be out sometime today though and I feel it highly important to move to that when it’s out, as it fixes some issues in 6.

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.

@Wayne-Workman That’s odd. I know that I had to create a different profile for LTSB but it certainly worked in LTSB. The profile I made in Win 10 Enterprise CB won’t work in LTSB and vice versa. Gotta create a new one. It’s lame I know. My login times are much longer than 4 seconds though. But I have a lot of customziations. Little common fixes and startup scripts and backgrounds and stuff, so my first login for any user is like 2 or 3 minutes, but only a few seconds after that first time.