Topics created by prince xyryl

@prince-xyryl I do not believe the built-in administrator account can be deleted, but you can disable it.

I am assuming you have something similar to this in your unattend file, correct?

<AutoLogon> <Password> <Value>notmypw</Value> <PlainText>true</PlainText> </Password> <LogonCount>3</LogonCount> <Enabled>true</Enabled> <Username>administrator</Username> </AutoLogon>

If you remove that block when you run sysprep with the generalize switch it should not enable the administrator account. Just make sure you create your other account before hand.

If you need the administrator account after sysprep you can disable it with this command: net user administrator /active:no

More information: https://technet.microsoft.com/en-us/library/Cc766343(v=WS.10).aspx

@ch3i said:

@prince-xyryl said:

additional question, The PRO and PRO SP1 of Windows 7 use the same key as listed ?** FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4**

KMS key depends on Windows version not release version.

Windows 7 Professional and Windows 7 Professional N have not the same key.

Okay. Thanks a lot. I’ll try to use the key in Win7 PRO sp1. Thansk again

If you need the profile data then you you will need an unattended file because the default is to not copy the data.

so I just run Sysprep after I install all the programs needed?

I will use this XP image on multiple different OLD hardware

Thanks

there are plenty of other programs to do this (silent application installs while pc is in use). I don’t use snapins in fog.

There isn’t a specific number but the total number of hosts in the task, but what you could check is that the FOGMulticastManager service is frunning as well.

[code]sudo service FOGMulticastManager stop
sudo service FOGMulticastManager start[/code]

A simple method is to create a folder in “c:\windows\inf” . I use “c:\windows\inf\xinf”.

Because Windows 7 recursively searches folders for drivers, and since Windows 7 searches “c:\windows\inf” by default, there is no configuration required other than to drop each extracted driver into its own folder inside “c:\windows\inf\xinf”.

Be aware, that some drivers are coded for both x86 and x64. Some will load x64 when x86 is required or vice versa, causing a failure of varying degree.

Some drivers for some versions of hardware will load the wrong version and brick the system. I’m looking at you Intel USB 3.0 eXtensible Host Controller (series 7 vs series 8).

I’ve dropped x86 and x64 drivers that play nice together into my xinf folder. I then use a vb script called from sysprep that detects specific needs for specific make/models that we have in service, that then performs installations and configurations, all the while using auto-logon.

Importantly, I disable and set to manual, the FOG Service before I close an image with sysprep. Reactivating the FOG service is the last thing my script does because the FOG Service will ungracefully interrupt any running scripts and force a restart when an image is deployed with naming and domain-joining enabled.

Okay in that case, I would build the image on a virtual and a physical machine. You need to enter audit mode and then sysprep your image and upload.

I recommend using a physical and virtual environment, as my machines I had to build the image on the physical machine (it has something to do with the hardware in the computer.) After doing so and uploading the image, I was able to image my problematic machines without errors.

We need more information, such as the OS the FOG Server is running on, what version of FOG, what things you’ve tried in relation to the FOG Server. We don’t really care so much about the Win2008 syste. How can’t it find the FOG Server? You don’t get the FOG Menu, tasks don’t run? What have you tried? Have you verified the dhcp and bootfile information is correct?

[quote=“prince xyryl, post: 36350, member: 25316”]up…

[B][COLOR=#ff0000]how? Where?[/COLOR][/B]

I cant see this on my FOG management page ([B] Download the FOG Client Service)[/B][/quote]

[url]http://youripaddressofyourfogserverhere/fog/client[/url]

Alternatively you can use the links at the bottom of the management page to get to the client.