Topics created by MLX

We considered this as well for certain tech savvy staff but ended up choosing not to. A phone call or support ticket into IT and we can set a PC to reboot and image from here with the web gui. Still quick and easy.

Hello
i’m very sorry to come back “so late”, i just didn’t have time to schedule this project. Now i’m busy with my branch.

Here is the infrastructure

France LAN (wan link with VPN) Abroad LAN
FOGserver ====== [ firewall ] :::::::::::::::::::::::::::: [ firewall ] ======= FOGstorage

I ran the installation on the remote ubuntu server to create a storage node. This one is not listed at the moment in my french FOGserver.

[URL=‘http://fogproject.org/wiki/index.php/FOGUserGuide#Advanced_Installations’]When reading the provided link abode (http://fogproject.org/wiki/index.php/FOGUserGuide#Advanced_Installations) i understand i have to create multiple tftp servers, because i have a VPN link, and both LANs are not on the same IP address range. But my abroad server can ping my french master FOG server.[/URL]
I’ll continue to write down what i do as i used to do with windows 7 :)[URL=‘http://fogproject.org/wiki/index.php/FOGUserGuide#Advanced_Installations’][/URL]

I just experienced this problem with a non-sysprepped Win7 image I was dealing with, and the steps listed here, [url]http://fogproject.org/forum/threads/windows-7-without-sysprep.862/[/url] , from lkrms, did the trick for me. Quoted below:

[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]"I wasn’t able to find bcdedit commands to replicate what sysprep does to the system BCD store, but here’s what I did to achieve the same result (using VirtualBox snapshots):[/COLOR][/FONT][/SIZE][/LEFT]

[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]1. Capture a snapshot of a working audit-mode Windows 7 machine. 32-bit or 64-bit doesn’t matter - the BCD data seems to be interchangeable.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]2. Boot your machine, open a command prompt and run: “C:\Windows\System32\sysprep\sysprep /generalize /quit”. The /quit is important; you want the machine to stay up after sysprep so you can collect the BCD store as sysprep leaves it.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]3. If curious, run: “bcdedit /enum”. You’ll see what sysprep has done to your BCD store.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]4. Capture your BCD store: “bcdedit /export C:\generalized.bcd”. Save the resulting file with your other deployment files; mine ends up living in C:\Windows\System32\sysprep alongside my unattend.xml etc.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]5. Feel free to discard the sysprep’d virtual machine. Restore to your step 1 snapshot or similar.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]6. As part of your FOG pre-capture workflow, when not using sysprep, run “bcdedit /import generalized.bcd”."[/COLOR][/FONT][/SIZE][/LEFT]