I’ve never seen the system partition bigger than 100mb other than sometimes an upgrade from vista or a beta might have been 200mb. It looks like you are using the OEM copy of Win7, do you have any way of using a stand alone copy? Are you sure you only have 2 partitions and not 3?
Posts made by jdd49
-
RE: Windows 7 image deployment slows way down at 25%
-
RE: Failed to deploy image to my clients
I think you may need to provide some more info:
You are deploying to 2 clients unicast or multicast?
What OS?
How many partitions?
What image type do you have set?
Same size hard drive as the original image or different? -
RE: NTLDR is Missing
Sounds like the MBR is not being restored properly. What image type are you using? single/multiple etc. Are you sure your image can be deployed to different machine types? If you take a hard drive out of a machine with the NTLDR problem and put it in a machine that does work with that image, does it boot?
-
RE: Adding drivers at the end of an restore.
Here is a solution that I currently use. I added an extra host option in the database. Similar to kernel options but called it scripts. Here I can add different scripts to different hosts or groups. That information is then appended to the bootimage in a variable called hostScripts. I created a new nfs share called scripts. In here are all of the different bash or shell scripts that can be ran after a host has imaged and before it checks out. Here is the function I call from my boot image.
if [ ! “$hostScripts” = “” ]; then
runScripts
fifunction runScripts()
{
mkdir /scripts
mount -o nolock,proto=tcp “$serverIP:/scripts” /scripts 2>/dev/mntscripts
echo “Running Script(s)”
sleep 1scriptCount=$(grep -o “,” <<<“$hostScripts” | wc -l)
scriptCount=$(( $scriptCount + 1 ))
echo “> Found $scriptCount Script(s)”
sleep 1
i=1
while [ $i -le $scriptCount ]
do
scriptArray[i]=$(echo $hostScripts | cut -d"," -f$i)
echo “> Running ${scriptArray[i]}”
sleep 1
cd /scripts
./${scriptArray[i]} $hd
i=$(( $i + 1 ))
sleep 1
done
}So if hostA had hostScripts=script1,script2,script3 set for it. It would run all 3 scripts that are stored on the server.
I know this has a lot info missing but this is a general idea of how you could do it.[/i][/i][/i] -
RE: Wireless labs & FOG
I want to try and help you out but don’t fully understand your question. You talk about login time and then about imaging. I don’t understand why you would need to turn off pxe booting. If these are two separate questions here is my solution.
[B]Wireless login time:[/B]
I’m not sure what kind of wireless solution you are using but you will need a high quality access point(commercial/enterprise) to handle that many connections. Otherwise you would need multiple access points in the same location. Other than that I can’t think of any ways to modify the login process.
[B]Strategies for imaging:[/B]
Laptops would obviously need to be imaged through a wire. Most laptops don’t need set for pxe booting. If they receive a wake on lan signal they automatically try to boot from the network. If yours don’t then could simply hit f12 or whatever your network boot shortcut key is. Finally if you do set it to boot from the network first, then the hard drive, after you have imaged the laptops they are no longer connected to a physical wire, therefore, PXE booting will see it has no connection and just skip to the next device which is your hard drive. So basically I’m saying there is no reason to turn pxe booting on and off. -
RE: Looping in attempt to image
Navigate to /tftpboot/pxelinux.cfg
Delete the file with the name as the mac address of your host -
RE: Modifying Image IDs
There are many ways to do this. Here is One:
[B]sudo apt-get install mysql-admin[/B]
[B]mysql-query-browser[/B]
Login then select Fog and then the images table, Change whatever you want -
RE: FOG_UPLOADRESIZEPCT
In the Fog UI select other information, then kernel updates. You can try both older and newer kernels.
-
RE: Fog/sysprep stops at computer name screen
I may be wrong here, I haven’t worked with Fog in a while and may not be familiar with any new features, but here goes.
If you don’t specify a computer name in your answer file windows will always stop and ask you for a name. If you put a * in for the name, one will automatically be generated by windows and you will not be asked for a name. When the computer reboots, the fog service will kick in and automatically rename the computer to whatever it is in your database.
Your quick reg should be set to 0 unless you are actually using quick registration. Ex, you have 10 new computers but don’t want to give them all names manually. Quickreg will automatically do this for you, but as far as i know it has anything to do with sysprep.
Is your computer name really set to PC-*. If it is that’s not right. The start should be replaced with a number if quick reg worked correctly.
Early name changer - I have not worked with this yet. As far as I know it has to do only with registry and not sysprep. Maybe you have this setting on and the pc’s registry is updated to the name in your database, then sysprep is just getting the name from that.
In summary, turn off quick reg, turn off name change early, and change your answer file computer name to a * You should be fine then.
-
RE: HOW TO ONLY CHANGE THE HOSTNAME ON THE CLIENT COMPUTERS ?
Is this for all computers or just some. If it’s all just remove the [FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_DOMAINNAME value. Are you using sysprep?[/COLOR][/FONT]
-
RE: Fog/sysprep stops at computer name screen
What do you have the computer name in your answer file set as?
-
RE: FOG_UPLOADRESIZEPCT
It really doesn’t matter. Neither option would effect speed nor the amount of data being transferred. It only effects what size hard drive it can be restored to. I find the best way to test speed issues is to use an isolated network. Use a simple 5 port switch or whatever u have, perferably gigabit, then do a unicast and see what kind of speed u get. If its still slow then start trying different kernels. Also some machines just simply don’t work as well as others. Try a different model and see how your speeds are.
-
RE: FOG_UPLOADRESIZEPCT
No. It has nothing to do with it. It is the padding b/w the amount of data used on the partition and the new size of the partition after a resize. Example, if you have a partition with 10 gigs of Data and the resize is set to 10, your image would be 11 gigs. You should keep this as small as possible that will still function.