Win-7 Deployment

13 posts / 0 new
Last post
kwisher
kwisher's picture
Win-7 Deployment

Hey Guys,

Getting ready to deploy our first Win-7 machines. Listened to your previous show about your experience. I was wondering were you installing OEM Windows on your machines? We currently have a MS Volume License and have a new KMS licensing server in place that all clients will get their Windows and Office activations from. I followed your image prep suggestions and was curious as to what type of O/S install you did. We also have a 2008 R2 AD server in place that is new this year.

Sincerely,

Kevin Wisher

Mark Cockrell
Mark Cockrell's picture
Win-7 Deployment

Yes, we used and OEM DVD with the KMS license key provide by Microsoft.  I used an external partition tool (GParted) to create a single NTFS partition, and then did a standard install from there.  We've had some issues with some of our machines not picking up the licensing information.  They say they're activated, then say they're not, then say they're not genuine, then say everything's fine.  It's very weird.

kwisher
kwisher's picture
Win-7 Deployment

Mark,

According to our outside tech support, I was told to install the VL version of Win-7 and not to use the OEM version that came with the machines. They also provided the following instructions for preparing my image:

1.       Download Windows 7 32/64-bit Professional volume license media from your Microsoft software center login area.

2.       Install fresh Windows 7, do not join domain.

3.       Enable administrator account then logon as administrator.

4.       Delete the account and profile of the user that was created during windows setup

5.       Apply all updates and base stuff like flash, Silverlight, Adobe reader, Java, Antivirus or whatever you like.

a.      Best practice would be to keep the base image as clean as possible and install apps after the image with gpo, sccm, or another      deployment tool.

b.      Make sure http://support.microsoft.com/kb/981542/ is installed

6.       If Office 2010 is installed in the image, and you plan on using KMS, Rearm Office..

a.      To rearm Office 2010, you only have to run ospprearm.exe in %installdir%\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform from an elevated command prompt.

7.       Clean up the image, clear temp files etc.

8.       Take an image in this state Non-syspreped so you can start easily again if sysprep or something fails, once sysprep you only get 3 tries, unless we add the skiprearm in the unattend, but if you have a backup in this state then you can just blow it back down.

9.       Unzip the win7sysprep.zip files to the c:\ drive.

10.   Verify the school name, and passwords in the unattend file. Also note this one is for x86 32bit arch.. if using 64 bit this unattend file will not work. (just replace x86 with amd64)

11.   Run the sysprep.cmd and it will kick off sysprep and shutdown the machine.

12.   At this point boot to pxe and take the image

13.   Deploy the image and test.

14.   Create a deployment task or a windows startup script that removes the sysprep files from the c:\ drive, as the files contains the password etc..

 

Hope this helps if you continue to have issues with activation.

Shawn Kibel
Shawn Kibel's picture
Thanks kwisher

Thanks for listing that info here.  Great stuff that would otherwise take a ton of digging to get right.

Mark Cockrell
Mark Cockrell's picture
Win-7 Deployment

That's so very Microsoft.  Bloated,overly complicated, and for the most part unneccessary!  I had forgotten when I made my original post, but we DID use the Volume License media from the Microsoft Web site rather than and OEM DVD.

kwisher
kwisher's picture
Win-7 Deployment

Did you guys run sysprep on your image before deploying it or just use fogprep? I followed the instructions I posted on my "base" image before uploading it to FOG and when I brought it down the first time and it finally booted to the desktop, I was greeted with a dialog box to supply the media for the FOG service installer. I pointed it to the install file but received an error about the service was already running. I saved an image before running sysprep as you can only sysprep an image 3 times. So I downloaded it again and the only thing I did different was to run fogprep before running sysprep. This proved to be the solution as I was able to successfully image 5 laptops.

The next step was to take my base image and add the software for our InterWrite/Projector systems for our teacher's machines. Followed my modified instructions and am now back to getting the fog service media prompt. Tomorrow I am going to try uninstalling the FOG client, running CCleaner and then reinstaling the FOG client.

If this doesn't work I am thinking about creating snapins for the extra software.

EDIT:

I found a link to some (hopefully) good info at the following link:

http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/

Also, it seems you don't need fogprep with FOG .32 so maybe that is part of my issue?? Going to try that and some of the info in the above link and report back.

kwisher
kwisher's picture
Win-7 Deployment

I didn't make much headway today. I kept getting the prompt for the fog service media after restoring my images. I believe it may have to do with selecting the "for me" option instead of "everyone" option during the FOG client install. I will know more tomorrow.

Shawn Kibel
Shawn Kibel's picture
Sysprep / FOGprep

We are also running 0.32.  We did not use sysprep at all.  We did use FOGprep.  Haven't had an issue at all with deployments.  With 0.32, FOGprep is not even supposed to be necessary although we did run it; not knowing we didn't need to.  It didn't seem to hurt at all though.  The "Everyone" option does sound like a possible cause.  We always use that option when installing the FOG client.  With the bugginess of Win7 user profile management, it wouldn't surprise me if this is causing the problem.  Keep us updated on your progress.

 

kwisher
kwisher's picture
FOG & AD

Hey Mark & Shawn,

I was wondering if you could post your AD settings you have in FOG? I have tried various times but have had no success getting the automatic addition of Win7 clients into AD after imaging. Win-XP does fine with script snapin I use but it seems Win7 stops after reimage at a screen for you to input the host name. It defaults with the name PC in the text field, which requires you to hit the enter button twice for it to proceed. After that FOG will change the host name and it will go ahead and add itself to AD with a script snapin (differnt than the one I use for XP).

Is your reimaging procedure for Win7 completely automated and hands-off?

 

TIA

Mark Cockrell
Mark Cockrell's picture
Re: FOG & AD

Yes, for us the whole process is automated.  A couple of things to check: Make sure that in the "FOG_AD_DEFAULT_USER" field you have it entered as DOMAIN\USER rather than just a user name.  Also make sure the "FOG_AD_DEFAULT_PASSWORD" is one that is properly encrypted using the FogCrypt.exe file found in the installation package.  We didn't really see a difference between XP and Win7 in terms of AD integration at all.  Good luck!

kwisher
kwisher's picture
Mark,

Mark,

Can you post or email me a screenshot of the AD settings you have in FOG?

Thanks.

Mark Cockrell
Mark Cockrell's picture
Re: FOG & AD

I don't want to paste the actual settings for fear of retribution from the tinfoil hats, but here is the screen with generalized data.

kwisher
kwisher's picture
I understand. Is there a way

I understand. Is there a way we can converse privately?

email: kevin dot wisher at gmail dot com

Log in or register to post comments