Better Task Deployment
-
this guide first got me started with using Virtualbox for building images
[URL=‘http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/’]http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/ [/URL]
-
So I tried setting this up last night, and was going good until I tried loading a sysprepped image. I did a “hybrid” approach to this. As of right now, I’m trying to get this to work without the FOG client, as we do not use the client at my place of employment. I’ve setup a generic image in a VM, install the programs, ran my updates etc. I then used this document and followed the instructions to make the autounattend file, [url]http://www.bauer-power.net/2011/02/how-to-sysprep-windows-7-on-easy.html[/url]. However, when the sysprepped image loads, I get a “Windows could not parse or process the (generalize)…” So i’ve been trying to figure out what has gone wrong. I think i’m going to just bite the bullet and create the same file in WAIK. So does everything that needs to be setup in WAIK need to be done under the specialize field? Or did you pretty much just do this portion from the guide you listed (of course, adjust as needed):
MY IMAGE IS x64 SO I ADDED THE AMD64 OPTIONS
-
Set Owner Information
-
Enable the administrator account and set password
-
Skip Activation
-
Hide License Info
-
Protect PC = 1 (basic protection)
-
Network Location = Work
-
Hide Wireless Setup
-
Set Language to UK
-
Show Windows Live = false
-
Skip Rearm = 1
This allows you to run sysprep more than 3 times on a machine, but i would recommend NOT using it.
[url]http://technet.microsoft.com/en-us/library/ff716063(WS.10).aspx[/url]
- copyprofile=true
copy profile will copy the administrator profile on sysprep and make it the default for any new user login. could be handy (i will use)
-
-
Try this sysprep guide
-
The guide worked perfectly. I just made some minor changes and got it configured the way I wanted to, so it’ll only prompt me for a PC name. However, the last hurdle, and apparently a well known issue, auto joining to the domain. From the way the answer file works, it’ll join the PC to the domain prior to being named, giving it a random name in AD. I’ve found the following command that can be used but have a question on one piece of it.
[B][I]NETDOM /Domain:YOURDOMAIN /user:DOMAINADMIN /password:DOMAINPASSWORD MEMBER [COLOR=#0000ff]COMPUTERNAME[/COLOR] /JOINDOMAIN[/I][/B]
I know that you have to have the AD tools installed to used this, as netdom is not part of windows 7 by default. However, to truly automate the process can the computer name in blue be set to something like %pcname% to automatically pull in the name of the computer? With us having close to 10,000 machines, we would like to have as much of the imaging process automated as possible. I’ve seen a powershell script and also a vbs script that claim to do the same thing, so i’m curious to see if the above post would work, or if there is an easier way yet to accomplish this task.[B][I] [/I][I][/I][/B]
-
Yeah i found it when I checked my Dropbox folder, its the guide that got me started with sysprepping.
Why do you not use the client, I only use it for joining domain? -
I’m on me phone at the moment, but first thought is. %localhost% maybe
-
It wasn’t up to me unfortunately. I was told that we can’t use the client based on the fact that it would cause to much “traffic” on the network with it checking in. Our way of imaging computers was very backwards. A group of us built FOG in an office to get bugs worked out until we were ready to demo it. The boss liked what he saw, the fact that it was much simpler to setup machines, and the fact that you wouldn’t have to remember cd’s or flash drives everywhere you went, we could PXE boot from any machine. So we were asked to put our server in the DC. When we brought up installing the client on the machines, we had a test pilot group of computers which we were very successful with. However, we were told that we were unsure of the traffic it would generate being on every machine. So we are forced to look at doing the images without the clients installed. BTW, I’m not in charge of our images, I was just sick of all the little steps we had to take to get an image installed on a computer, hence why we put FOG together
-
oh fair enough, you could mention that you can install the client to enable domain joining, but disable all other services (to stop any other network traffic). PC can also use name given in FOG Webui, then join domain with that name, thats what I have set up.
It use to be backwards at my old place of work, that’s what led me to FOG
-
Falko, would you happen to have that guide still from your DB? I had my computer crash and lost all my guides/notes I had made and found. Just trying to rebuild the collection. Being a fully encrypted RAID 0+1 setup, there wasn’t much chance of retrieving the data
Thankfully, the VM’s are on a separate drive so I still have those. -
-
Awesome, thanks much.
-
no probs