+ Post New Thread
Page 4 of 4 FirstFirst 1234
Results 46 to 53 of 53
O/S Deployment Thread, Fog and windows 7 in Technical; You dont need netdom anymore just have the newest fog client on the PC .32. You will need to update ...
  1. #46

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    You dont need netdom anymore just have the newest fog client on the PC .32. You will need to update the hostnamechanger.dll. C# needs to be .net2 then you create it.

  2. Thanks to marlwoodadmin from:

    saadi (31st October 2011)

  3. #47

    Join Date
    Oct 2011
    Location
    west bromwich
    Posts
    2
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks mate didn't know that. Been using netdom for no reason then. Is this the same with XP? Only I have had issues with XP and the latest version of FOG. Basically FOG hasn't been adding the machines to the domain and in some cases it doesn't even rename the machines. But the same machines join the domain if I use a windows 7 image.

  4. #48

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    You need netdom if you are using XP (i think). Could it be that the username format to join the domain is different? On the web console Win7 works like domain\username but xp was just username. Again i think this i correct as now it is set up i rarely have to change anything.

    We are using mulitiple FOG clients for various bit of the setup. the FOG server is installed as .31; the init.gz is .29; the client on the PC is .32. FOG doesnt seem to care if all these are mismatched.

    Reason:
    FOG server .31 was used because it was the newest one when we set it up
    init.gz .29 was used because the uploads and deployments are quicker than any other version we have tried
    Client .32 was used to get the PCs to join the domain even if there was a computer account in AD with the same name

  5. #49

    Join Date
    Nov 2010
    Posts
    482
    Thank Post
    64
    Thanked 72 Times in 59 Posts
    Rep Power
    35
    Quote Originally Posted by GreyFox View Post
    Hi again Chris,

    Well I've been trying this and I just can't get it to work. Keep getting:

    'Windows Failed to start. A Recent hardware or software change might be the
    cause. To fix the problem:

    1: Insert your Windows disc ...blah blah
    2: blah
    3:blah

    If you do not have this disc, contact your system administrator or computer
    manufacturer for assistance.

    Status: 0xc000000e

    Info: The boot selection failed because a required device is
    inaccessible.'

    Which I believe is the reason I gave up trying to use FOG for our deployment. Any ideas?

    There is another topic open, and unsolved here;
    Fog windows 7 and ntfs resizable

    Thank you

    Grey Fox
    In case somebody in the future finds this (hello!), I think that error is caused by the image type being set to single image. Try specifying a multiple partition image (win7 likes a separate boot partition at the start of this disc. Forget it and it doesn't want to boot).

  6. #50

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    You CAN use single resizable image. But you MUST sysprep the image with the shutdown switch and then upload the the image. works hunky dory then!

  7. #51

    Join Date
    Nov 2011
    Location
    Winchester
    Posts
    22
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    7

  8. Thanks to kv102t from:

    marlwoodadmin (19th April 2012)

  9. #52

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    That looks a lot like documentation to me...

  10. #53

    Join Date
    Aug 2012
    Location
    Missouri
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Fogprep issues

    Let me preface by saying I am very new to network administration and don't have more experienced people with me to assist, so please forgive what probably seems like basic questions;

    I am trying to image Windows 7 machines using a FOG server (.32). I already ran imaging on them, but thought that it would work the same as XP (i.e. didn't do anything with sysprep or FOGprep), and they are currently not working. I need to get them going in the next day or two for the teacher that will be using them. I'm trying to run FOGprep now on the one machine that I didn't image so I can upload an image correctly and redeploy it to the other 7 computers that are fouled up, but I am getting the message "Requested registry access is not allowed" (even when I tried to run it on the admin account). I doublechecked the registry access settings, and it wasn't set up to block anyone's access.

    Does anyone have ideas on how to fix this issue, and is there anything else I need to do to have the computer ready to upload its image? I've read several blogs about it, and they all seem to be based on imaging computers that are just getting everything installed on it for the first time.



SHARE:
+ Post New Thread
Page 4 of 4 FirstFirst 1234

Similar Threads

  1. FOG, Windows XP and AD
    By wellscs in forum Windows
    Replies: 2
    Last Post: 14th December 2010, 10:32 AM
  2. Replies: 3
    Last Post: 30th September 2010, 12:44 AM
  3. Replies: 2
    Last Post: 18th August 2010, 08:49 AM
  4. [Fog] Fog Documentation: How to delete a group of computers in FOG
    By ssx4life in forum O/S Deployment
    Replies: 1
    Last Post: 9th November 2009, 02:59 PM
  5. [Fog] FOG
    By CheeseDog in forum O/S Deployment
    Replies: 5
    Last Post: 3rd March 2009, 10:54 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •