Registry error upon FogPrep
-
I am getting the following during FogPrep. This is happening on my Dell AIO 9010, and 390’s.
[ATTACH=full]326[/ATTACH]
any ideas? Thanks!
[url=“/_imported_xf_attachments/0/326_Capture.PNG?:”]Capture.PNG[/url]
-
What version of windows? What version of FOG? Are you using sysprep? You may not even need to use FogPrep depending your answers.
-
WIN7 only, Version .32, and frankly I hate to admit it but I haven’t found enough info on sysprep to learn how to use it.
I have gone ahead and just forced an upload just to see what happens but currently with a Dell 390 image it is taking about 1 hour and 20 minutes, whereas most of my images take no longer that 25 min.
I also have an issue with ‘disk information’ on the Dashboard not updating (just continues to loop) which makes me wonder if I have already exceeded my 1tb , which goes into the issue if this is causing my 390 image to take so long , which then goes to the FogPrep thing, and blaa, bla, blaaaaa…
thanks for the response!!
-
[quote]WIN7 only, Version .32, and frankly I hate to admit it but I haven’t found enough info on sysprep to learn how to use it.[/quote]
Then stop and learn, it is an integral part of imaging with the latest versions of windows. However I receive mixed signals on wheather it is entirely required with FOG imaging. It’s a good idea because some software and hardware will be dependent on a CMID (ClientMachineID) which is unique to each machine and running the sysprep process frees this information to be registered by the current machine. Sysprep can only generally be ran a total of 3 times, that is why I make the recommendation I do with the Virtual set up , that way you can take snapshots and revert back when your sysprep doesn’t work.
Also KMS activation will only allow one CMID to be registered, each machine has to be unique to activate.
I have a walkthrough I have been working on for my co-workers who have yet to even set up a fog server, so it’s probably a huge waste of time but I could let you take a look at it as it details the sysprep process with FOG 0.32 very well if you are interested.
As far as your fog server reporting it’s freespace, it’s typically wrong, I have one image under 30 gb on my server and it thinks that 95% of the freespace is full… silly server, not really a big deal so I haven’t looked into resolving this but I know a few others have.
-
Although your response is somewhat a mixed message about sysprep :
[I]“However I receive mixed signals on where it is entirely required with FOG imaging.[/I]
[I]I have a walkthrough I have been working on for my co-workers who have yet to even set up a fog server, so it’s probably a huge waste of time but I could let you take a look at it as it details the sysprep process with FOG 0.32 very well if you are interested.”[/I]I’ll try anything once and some things twice.
Kinda funny cus my current 390 image is reporting almost 300gb
-
Sorry my fingers tend to get a little excited. What I was trying to say is I haven’t been given a solid answer if sysprep is required with FOG.
I sent the walkthrough to your inbox, some of it may not be required, if you are not a novell environment, and somethings may need tweaked but this will give you a base to work from.
I’m trying to work with the sysprep so I don’t have to use FOGPrep
-
Sysprep is not required for FOG. FOG will image computers just fine without sysprep. Windows is what needs sysprep, more specifically Windows on different hardware, Windows Activation, WSUS services, KMS activation, and other stuff.
If you use the new Volume Licensed media to install windows, it has a 1000 rearm limit, as opposed to the old 3 rearm limit. If you have volume licensing agreement, I strongly urge you to update your install media and download the new installs from microsoft. They also come with SP1 included to save you some time.
When I first started with FOG 0.32 and Windows 7, I was not able to preserve the OEM key because FOG would not image the laptops due to the OEM and windows recovery partitions. So I installed Windows from scratch and cloned without sysprep and used our MAK key to activate all 700 of our computers. Each summer, we reimage all of our laptops, and so we ran out of activations. I call/email to MS licensing, and they increased our activation count to allow more MAK activations. But really, these are re-activations of the Windows on the same machines. The problem here is that every year, when we re-image our laptops, we have to up our activation counts and deal with MS licensing.
When we installed the KMS server to avoid having to up our MAK count each year, we ran into problems that all the machine had the same CMID and we never got to the 25 activations minimum for KMS to actually activate the machines. I had 700 machines all using one CMID.
I am redoing our images this year to be able to use Sysprep to create unique CMID’s so KMS will work for our Windows 7 machines. You really only need the small part of sysprep which is to generalize and OOBE. You don’t need to learn about all the other steps unless you just really want to.
-
Yes , I too have 700+ machines and am going through reimaging issues. I agree that sysprep appears to be overkill or unnecessary for FOG. After using FOG, which I inherited, for the last year it seems I am running into more and more issues that has me concerned whether or not FOG is worth the trouble; but then again I have nothing else to try.
thanks
-
It depends on your goals for sysprep and FOG.
My goal is to make an image for a particular brand and model of laptop that is as complete as possible (drivers and software) so I can blast it out to student laptops as quickly as possible and have as little to do after imaging as possible.
Others’ goals are to have a hardware generic base image, and then use utilities after imaging to install drivers and software and run complex scripts to finalize the machine before sending it to the end user.
I have plenty of storage space but little time over the summer to image 5 different models of laptops. I have even less patience to wait on updates and scripts that may fail for any variety of reasons.
If it wasn’t for KMS activation for Windows 7, I would probably skip sysprep altogether. We are upgrading our domain this summer to support Active Directory Based Activation for all our Windows 8 tablets and Office 2013, but our Windows 7 laptops are stuck with KMS for now.
-
‘My goal is to make an image for a particular brand and model of laptop that is as complete as possible (drivers and software) so I can blast it out to student laptops as quickly as possible and have as little to do after imaging as possible.’
I’m the same , I really don’t have the time to create and run scripting , and also have little time to tweak and R&D . My FOG install runs well just as long as I don’t get off the reservation too much. I think my Dell 390’s , 9010’s and all of my laptops are requiring more TLC than I realize.
