Village_Idiot

Hey Steve, Thanks for replying. Sorry, I'm quickly trying to familiarize myself with the commands and pretty much trial and error. I tried removing the /d and using just the path but ended up with "The server process could not be started because the configured identity is incorrect. Check the username and password." I then went to ss64 and found an example where /d was being used. Start an application and specify where files will be saved (Working Directory): START /Dc:\Documents\ /MAX "Maximised Notes" notepad.exe The only change necessary seemed to be in removing the space between /d and the path to the file. @echo off start [b]/dC:\Image\ps\[/b] AdobeSerialization.exe --tool=VolumeSerialize It worked! I've already tested Photoshop and Illustrator, and will be testing the other Adobe applications. On a separate note, I did find I am having trouble creating the Adobe After Effects serialization using the AAMEE. Wondering if it is just my Adobe medium I'm working with.

For myself, I used the AAMEE to create a Photoshop TRIAL package as well as the serialization. Installed the Photoshop TRIAL on my master image. Just trying to test out the serialization, I would sysprep the machine and reboot but found it hanging at "Windows is finalizing your settings" stage (just prior to loading the user's desktop). Based off of a user named StickyNote in another forum, I did the following: TEST #1 [1] Placed the AdobeSerialization.exe and prov.xml into C:\Image\ps folder [2] Within the same C:\Image\ps folder, I created a CS6_PS_Serialize.cmd with the following @echo off start /d C:\Image\ps\AdobeSerialization.exe --tool=VolumeSerialize [3] Created a SetupComplete.cmd with the following @C:\Image\ps\CS6_PS_Serialize.cmd RESULT : Hanging at "Windows is finalizing your settings...." ____________________________________________ I found the following at some other site, TEST #2 @echo off start /d "path_to_file" AdobeSerialization.exe --tool=VolumeSerialize del AdobeSerialization.cmd [1] In my CS6_PS_Serialize.cmd, @echo off start /d C:\Image\ps\AdobeSerialization.exe --tool=VolumeSerialize [2] I then altered the SetupComplete.cmd start c:\Image\ps\CS6_PS_Serialize.cmd RESULT: Command window open at C:\Windows\System32 complaining about "Windows cannot find '--tool=VolumeSerialize'. Make sure you typed the name correctly, and then try again." Help......what am I missing or doing wrong?

This is a MAJOR PITA! Last semester's startup - I nearly about died trying to figure out what was causing it to go into this endless loop. After many hours of searching I came across a small mention by someone regarding corrupt registry, but thought nothing of it. No solutions were posted. I ended up calling up Microsoft - and lo' and behold, they had a hotfix available that fixed registry entries that would cause Win 7 sysprepped images to go bonkers. Sorry I don't have the exact KB article and I haven't touched Win 7 imaging for months - busy with other tasks. There are a couple of posts at other forums (not sure if I can name them) but that is where credit is due. I now have the ACTUAL SOLUTION to this problem. This solution will actually tell you exactly what registry key is causing your sysprep to fail, so then you don't have to slowly install every program until you find the problem -- especially since this didn't work for me because my problem has been intermittent. This issue is caused by certain registry keys that are either: a) Larger than 8kb b) Set with incorrect permissions c) Corrupt in some way For me, the problem was intermittent (same registry key would sometimes cause the issue and sometimes not - must be corrupt sometimes) so it was impossible to tell what program was doing it. Luckily, there is a log you can look at that will tell you exactly what registry key is erroring out. Here are the steps for getting the log you need to see: When you see the error message, do the following: 1.) Push Shift+F10 to get to a command prompt 2.) Navigate to C:\windows\Panther 3.) Find the Setup.etl file and find a way to copy this file off of the system (I copied it to the D:\ partition and used Ghost to gather that partition and get the file off) 4.) Copy the setup.etl file from the corrupted system to another computer that has Windows 7. Put it on the root of C:\ for easiest access. 5.) Open a Command Prompt on the Windows 7 computer. 6.) Navigate to the root of C:\ (or wherever you saved the file) 7.) Type "tracerpt setup.etl -o logfile.csv" 8.) Close the command prompt and open up logfile.csv in your text editor of choice. 9.) Look through the log file (towards the end probably) for messages that say "Failed to process reg key or one of it's decendants" For me, the exact eror looked like this: "Failed to process reg key or one of its descendants: [\REGISTRY\MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000200\Profiles\@My profile]" If you search for "reg key" or "failed to process" you should find the failure. 10.) Remove this software from your image, or find out how to get the registry key that is failing to work properly. After this, you should be able to properly identify any problem keys and remove/workaround them on your image. Lastly, I was using WDS and WAIK. Slow.....but free. Didn't have the time to look into other deployment methods at the time.

Half XP SP3 and half MAC Haven't had the time to test out Win7 - no timetable on roll-out. Top person here also on Vista.

Thanks everyone for the welcome! Hopefully be able to contribute in the future, but in the meantime, I'll need your help.

Wandering around by googling NetOp.....and came upon this site. Have been browsing the forums for a couple of days or so, and found it to be filled with lots of great stuff. Currently given the task of testing out NetOp, so doing some research now. Saying a hello to everyone from Toronto, Ontario, Canada.