If you don’t have overlapping subnets between the two networks it may be easier to setup routing so that both networks can see and use the fog server.

I don’t know if there is a way to make Fog work the way you are proposing using another interface.

[quote=“eric0626, post: 3807, member: 357”]KMS does not use SID, but it uses CMID instead. Thus, you don’t have to sysprep the image if you want to KMS, you can just simply rearm the OS before uploading the image.[/quote]

Eric, you are right about the fact that KMS does not use the SID, but CMID instead. This does not change the fact that sysprep is necessary, as CMID is also changed by sysprep. Having the same CMID on all computers results in KMS not counting.

Rearming the computer will create a new CMID, but this is not supported by MS. The recommended way is to rebuild your image with sysprep /generalize and no <SkipRearm>. The last note on the [URL=‘http://support.microsoft.com/kb/929829’]KB929829 [/URL]might be confusing though.

Regards, Bjorn

Also is it possible that the SATA controllers are configured differently? You might pop into the BIOS and check that out and confirm that they are all set the same as the laptop you built the image on.

Try to check the command file for the machine in question.
/tftpboot/pxelinux.cfg/01-XX-XX-XX-XX-XX-XX (The file is named after the MAC of the machine)

Within that file check to make sure all settings are correct. Like DNS=(should be your DNS on Your network and not the remote DNS)

Another thing to check: is there something broadcasting on the remote network that could interfere with the traffic?

I have a bunch of these ST250LT007 Seagate drives (the same Momentus line of drives, but with no encyption) and they work just fine. However, 4K advanced format drives are not supported in FOG yet. You’d have to use FOG .33 (beta still) to image those drives. That is what I am using now and it is working. The beta is not “feature complete” yet, but 4K drive imaging works.

I’d recommend downloading the beta release to a spare system and doing a few image tests. You could report your success/failures to this forum post:

[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/page-4#post-3691[/url]

If you need help getting the latest beta release down, just let me know.

Have you tried setting the image type to “multiple partition image - single disk (not resizeable)”? This usually works for everything.

[quote=“astrouga, post: 3670, member: 907”]Sounds like you need to modify your existing DHCP server so it can point to your FOG server:

[url]http://www.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG[/url][/quote]

This should do the trick

If you do try the .33 beta please provide feedback on your experience/thoughts to the thread above

[quote=“InjecTioN, post: 3642, member: 1175”]This solution would be even better![/quote]
[B][URL=‘http://fogproject.org/forum/attachments/dp_install_tool-txt.94/’]yeah its in the DP_Install_Tool.txt[/URL][/B]

Jigar:
I would use the multiple partition option. Leave the OS set to Windows 7. It never fails.

I think kirksec is right regarding the single partition settings. I have only ever been able to get it to work in that situation. In the past it was always problematic for me so I stopped using it.

–astrouga

Well I solve my own problem! Tends to happen a lot.

The problem ended up being the Bios version wasn’t supported, and it was the latest and greatest.

The fix, I remembered an option in Clonezilla to use PXE boot. So for the giggles I booted off the Clonezilla CD, selected iPXE boot. then FOG started working, but an error came along saying “unsupported bio’s version”. So i let it sit for a little bit, under 2 minutes and it just started going! It’s imaging the computer right now as I type.

I find this quite remarkable and think it should be sticky’d. This will help a lot of people with these problems.

Yes, it kinda defeats what FOG is trying to accomplish, but hey it still beat going through all the lines of clonezilla to get an image rolling.

And my other error was due to my user in FOG being the same on ubuntu, same password and all. So that’s all fixed and ready to go!

From what I read about it on other sites, youre better off using FOG for storage. Is that for backup purposes?

Hello,

If your computers are all the same, you can use FOG. I’m doing this already with Optiplex, etc.
Here is what I do : [url]http://fogproject.org/forum/threads/windows-7-deploy-error-0xc000000e-boot-selection-failed-because-a-required-device-is-inaccessible.462/#post-2210[/url]

Excellent! Glad that worked out for you. 🙂

Hello there,
any solutions to the problem?? I’m having the same problem now.

I took the WD harddisk from one of the GX745’s that worked, put it in the GX755 that has the issue, then reimaged with the same image, works fine; I then took the Seagate harddisk that was originally in the GX755 and put it in the GX745 and tried to reimage, and it works as well…go figure, am totally confused as to why FOG images the Seagate fine in the GX745, but not in the GX755…

Hi Mark
I have exactly the same problem and know for fact that it’s not the FOG service.
I finaly fix it by putting the password for account in registry under HKLM\software\microsoft\windows NT\current version\winlogon
I setup the key called DfaultUserPassword.

there is a program called windowsautologin.exe that does all that for you.
I also noticed that the password will be removed from registry after the number of autologon is over.

I appreciate if you tell mw what solution you found.
thanks