Jump to content

thetob

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

10 Good

About thetob

  1. It worked perfect! I removed everything(name,domain etc) from sysprep and let FOG handle that part instead. FOG service rebooted as you guys said and joined the domain. Thanks again guys!
  2. You guys are awesome! I will try it later this afternoon and hope i get it right! I will let you know about the results! Big thanks for your nice attitude and willing to help!!
  3. Thank you for a quick answer! Im not sure what the "FOG service" is, u mean that FOG client installation? So if i understand this correct, it should be like this: - Install XP - Updates etc - Install Fog service - Run an working sysprep(been used for this company for about 1 year without problem) - Reboot and image it - Boot and let the sysrep and fog service run
  4. Hi! I have one annoying problem with fog. I have choosen to run fog instead of symantec ghost because of expensive licensing etc. And man i like FOG, but... Im in charge of couple companies and i choose to test fog on a XP-only company. I do all necessary things that are needed for the ghost image and it still wont work. - Install XP - Updates etc - Run an working sysprep(been used for this company for about 1 year without problem) - Image it - Boot and the sysprep runs When i enter windows i can choose to login local or to the domain. When i try to login in to the domain it wont work because the computer(name) havent been added to AD for some reason. So i have to login local and rejoin the computer to the domain and that works perfect! Is this a common problem or do i just suck Because even if this sysprep has worked on symantec it shouldnt be any problem with fog. Anyone has any ideas? Regards, Tobias
×
×
  • Create New...