+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 53
O/S Deployment Thread, Fog and windows 7 in Technical; Do you have anything in the OU field in FOG? If it's populated and a computer object already exists for ...
  1. #31
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    Do you have anything in the OU field in FOG?

    If it's populated and a computer object already exists for that PC then you'll get an error on joining the domain. It works fine if there's not already a computer object though.

    If you look in the fog.log on a failing PC it should give you an error code. You might need to increase the log size first as it over writes itself quite quickly - change the entry in c:\program files\fog\etc\config.ini

    If you're getting an error 2224 (this is what you get when the OU field is populated and a computer object already exists) then there's a fix which I linked to a few posts above.

    HTH...

    Chad

  2. #32

    Join Date
    Mar 2011
    Location
    UK
    Posts
    39
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi Chad,

    No, OU fields are empty, or at least are at host level. We have (now had) a value in under 'Fog Settings', but I always removed the OU bit and updated before starting the deployment.

    I've added the fix you suggested at line 512 anyway, just to see what happens, as well as clearing the OU settings.

    Will see how it goes and report back. I'll extend the log as well if need be, thanks for the advice.

    Thank you

    GreyFox

  3. #33
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    It took me a few tries to get it working too but I have no issues now. I updated the FOG wiki a while back to clarify the format of the fields (e.g. username needs to be domain\username, domain name needs to be in FQDN format) so if they all look good, the next port of call would be the fog.log file.

    Many of the errors trapped in this don't have a friendly text explanation though. I found a few more explained after searching for "JoinDomainOrWorkgroup" which is the call used to join the domian.

    Have a look at one of the replies near the bottom of this post for an explanation of a few more of the numeric codes.

    Good luck!

  4. #34

    Join Date
    Mar 2011
    Location
    UK
    Posts
    39
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hmm, getting a little bored of this now

    Code:
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for MODDebug.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : PrinterManager.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for PrinterManager.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : SnapinClient.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for SnapinClient.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : TaskReboot.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for TaskReboot.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : UserCleanup.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for UserCleanup.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : UserTracker.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for UserTracker.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : config.ini
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for config.ini
     05/05/2011 14:27 FOG::ClientUpdater Zero byte response returned
     05/05/2011 14:27 FOG::ClientUpdater 0 new modules found!
     05/05/2011 14:27 FOG::ClientUpdater Client update will be applied during next service startup.
     05/05/2011 14:27 FOG::ClientUpdater Client update process complete, exiting...
    After a restart I get

    Code:
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for MODDebug.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : PrinterManager.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for PrinterManager.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : SnapinClient.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for SnapinClient.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : TaskReboot.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for TaskReboot.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : UserCleanup.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for UserCleanup.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : UserTracker.dll
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for UserTracker.dll
     05/05/2011 14:27 FOG::ClientUpdater Checking Status : config.ini
     05/05/2011 14:27 FOG::ClientUpdater No update found on server for config.ini
     05/05/2011 14:27 FOG::ClientUpdater Zero byte response returned
     05/05/2011 14:27 FOG::ClientUpdater 0 new modules found!
     05/05/2011 14:27 FOG::ClientUpdater Client update will be applied during next service startup.
     05/05/2011 14:27 FOG::ClientUpdater Client update process complete, exiting...
     05/05/2011 14:29 FOG Service Engine Version: 3
     05/05/2011 14:29 Starting all sub processes
     05/05/2011 14:29 14 modules loaded
     05/05/2011 14:29  * Starting FOG.AutoLogOut
     05/05/2011 14:29  * Starting FOG.SnapinClient
     05/05/2011 14:29  * Starting FOG.DirCleaner
     05/05/2011 14:29  * Starting FOG.DisplayManager
     05/05/2011 14:29  * Starting FOG.GreenFog
     05/05/2011 14:29  * Starting FOG.GUIWatcher
     05/05/2011 14:29  * Starting FOG.HostNameChanger
     05/05/2011 14:29 FOG::GUIWatcher Starting GUI Watcher...
     05/05/2011 14:29  * Starting FOG.HostRegister
     05/05/2011 14:29  * Starting FOG.MODDebug
     05/05/2011 14:29  * Starting FOG.PrinterManager
     05/05/2011 14:29 FOG::MODDebug Start Called
     05/05/2011 14:29 FOG::MODDebug Sleeping for 100 Seconds
     05/05/2011 14:29  * Starting FOG.SnapinClient
     05/05/2011 14:29  * Starting FOG.TaskReboot
     05/05/2011 14:29  * Starting FOG.UserCleanup
     05/05/2011 14:29 FOG::TaskReboot Taskreboot in lazy mode.
     05/05/2011 14:29 FOG::TaskReboot Starting Task Reboot...
     05/05/2011 14:29 FOG::PrinterManager Starting interprocess communication process...
     05/05/2011 14:29 FOG::HostRegister Starting host registration process...
     05/05/2011 14:29 FOG::ClientUpdater Starting client update process...
     05/05/2011 14:29 FOG::ClientUpdater Sleeping for 477 seconds.
     05/05/2011 14:29 FOG::PrinterManager  interprocess comm startup: OK
     05/05/2011 14:29  * Starting FOG.UserTracker
     05/05/2011 14:29 FOG::UserTracker Starting user tracking process...
     05/05/2011 14:29 FOG::UserCleanup Sleeping for 15 seconds.
     05/05/2011 14:29 FOG::DisplayManager Starting display manager process...
     05/05/2011 14:29 FOG::HostnameChanger Starting hostname change process...
     05/05/2011 14:29 FOG::HostnameChanger Yielding to other subservices for 5 seconds.
     05/05/2011 14:29 FOG::DirCleaner Sleeping for 45 seconds.
     05/05/2011 14:29 FOG::AutoLogOut Starting process...
     05/05/2011 14:29 FOG::GreenFog Sleeping for 55 seconds.
     05/05/2011 14:29 FOG::SnapinClient Starting snapin client process...
     05/05/2011 14:29 FOG::SnapinClient Sleeping for 468 seconds.
     05/05/2011 14:29 FOG::DisplayManager Attempting to connect to fog server...
     05/05/2011 14:29 FOG::HostRegister Exiting because only 1 mac address was found.
     05/05/2011 14:29 FOG::TaskReboot Attempting to connect to fog server...
     05/05/2011 14:29 FOG::PrinterManager Attempting to connect to fog server...
     05/05/2011 14:29 FOG::UserTracker Attempting to connect to fog server...
     05/05/2011 14:29 FOG::UserTracker Module is active...
     05/05/2011 14:29 FOG::AutoLogOut Module is active...
     05/05/2011 14:29 FOG::DisplayManager Module is disabled globally on the FOG Server.
     05/05/2011 14:29 FOG::AutoLogOut Timeout value is Zero, disabling module.
     05/05/2011 14:29 FOG::PrinterManager Module is active...
     05/05/2011 14:29 FOG::PrinterManager Starting printer manager...
     05/05/2011 14:29 FOG::PrinterManager Yielding to other services for 36 seconds.
     05/05/2011 14:29 FOG::TaskReboot Module is active...
     05/05/2011 14:29 FOG::TaskReboot Attempting to connect to fog server...
     05/05/2011 14:29 FOG::TaskReboot No job exists for 00:30:1B:46:80:15
     05/05/2011 14:29 FOG::TaskReboot No task found for client.
     05/05/2011 14:29 FOG::HostnameChanger Attempting to connect to fog server...
     05/05/2011 14:29 FOG::HostnameChanger Module is active...
     05/05/2011 14:29 FOG::HostnameChanger AD mode requested, confirming settings.
     05/05/2011 14:29 FOG::HostnameChanger Hostname is up to date
     05/05/2011 14:29 FOG::HostnameChanger Attempting to join domain if not already a member....
     05/05/2011 14:29 FOG::HostnameChanger Domain Error! ('Unknown Error' Code: 1326) 
     05/05/2011 14:30 FOG::UserCleanup Starting user cleanup process...
     05/05/2011 14:30 FOG::UserCleanup Attempting to connect to fog server...
     05/05/2011 14:30 FOG::UserCleanup Module is disabled globally on the FOG Server, exiting.
     05/05/2011 14:30 FOG::PrinterManager Management level = 0
     05/05/2011 14:30 FOG::PrinterManager This host is set to NO MANAGEMENT, we will exit now.
     05/05/2011 14:30 FOG::PrinterManager Major printing operations complete, moving to tracking mode.
     05/05/2011 14:30 FOG::DirCleaner Starting directory cleaning process...
     05/05/2011 14:30 FOG::DirCleaner Attempting to connect to fog server...
     05/05/2011 14:30 FOG::DirCleaner Module is active...
     05/05/2011 14:30 FOG::DirCleaner Determining which directories should be cleaned...
     05/05/2011 14:30 FOG::DirCleaner No directories are configured to be cleaned.
     05/05/2011 14:30 FOG::DirCleaner Starting directory cleaning loop...
     05/05/2011 14:30 FOG::DirCleaner Module has finished work and will now exit.
     05/05/2011 14:30 FOG::GreenFog Starting green fog...
     05/05/2011 14:30 FOG::GreenFog Attempting to connect to fog server...
     05/05/2011 14:30 FOG::GreenFog Module is active...
     05/05/2011 14:30 FOG::GreenFog No actions were found.
     05/05/2011 14:30 FOG::GreenFog No tasks found after validation!
     05/05/2011 14:30 FOG::UserTracker Event: LOGIN for SN68G-WIN7\Administrator
     05/05/2011 14:30 FOG::UserTracker Record processed by server!
     05/05/2011 14:30 FOG::PrinterManager New user detected: SN68G-WIN7\Administrator
     05/05/2011 14:30 FOG::PrinterManager Waiting for tray to load...
     05/05/2011 14:31 FOG::MODDebug Reading config settings...
     05/05/2011 14:31 FOG::MODDebug Reading of config settings passed.
     05/05/2011 14:31 FOG::MODDebug Starting Core processing...
     05/05/2011 14:31 FOG::MODDebug Operating System ID: 6
     05/05/2011 14:31 FOG::MODDebug Operating System Minor: 1
     05/05/2011 14:31 FOG::MODDebug MAC ID 0 00:30:1B:46:80:15
     05/05/2011 14:31 FOG::MODDebug MAC POST String: 00:30:1B:46:80:15
     05/05/2011 14:31 FOG::MODDebug A user is currently logged in
     05/05/2011 14:31 FOG::MODDebug Username: SN68G-WIN7\Administrator
     05/05/2011 14:31 FOG::MODDebug Hostname: SN68G-WIN7
     05/05/2011 14:31 FOG::MODDebug Attempting to open connect to: http://FOG-SERVER/fog/service/debug.php
     05/05/2011 14:31 FOG::MODDebug Server responded with: Hello FOG Client
     05/05/2011 14:31 FOG::MODDebug Module has finished work and will now exit.
    Just noticed the bit highlighted in red. After doing some searching, that comes up with "Case 1326 strErrorDescription = "Logon failure: unknown username or bad password"" So I'm assuming that's the same code in FOG. Just found a post of Sourceforge with someone having the same problem, and turned out that the encrypted password is wrong. This could be true for us I suppose after I loaded the settings from a saved file!! Will be trying that now.

  5. #35

    Join Date
    Mar 2011
    Location
    UK
    Posts
    39
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Well I feel like a right muppet!
    Turns out it was the damn password after all

    Was certain I'd updated my file with the new password.

    Thanks for suggesting looking at the log - although the first one didn't show anything, so may have just dismissed.
    Cheers all for your help!

    I'll have to have browse around and see if I can repay the favour to anyone with something else.

    Many thanks again!

    GreyFox

  6. #36
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    Glad you got it going!

    The error codes reported back in the log could be definitely be clearer - it's not exactly an "Unknown error" when you can google and it tells you it means it's a logon failure. I'll perhaps submit a patch to clarify the "unknown" ones.

    Note that if you want to increase the size of the fog.log file throughout your entire estate, you can upload a tweaked config.ini to the FOG server under FOG Settings/client updater and the clients will pull it down as an update.

    Cheers,

    Chad
    Last edited by Chad; 6th May 2011 at 03:41 PM. Reason: typo

  7. #37

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by ChrisMiles View Post
    Once you have these lines all you need to do is one by one image you different models with your base image, install drivers, re-sysprep and re-upload. Then move on to the next model. By the time you've imaged and re-uploaded your image from one of each of your different models the windows 7 will have device information and drivers for everything you need.
    Thanks for being so active on the forum ChrisMiles. Its been a great help reading your advice. Thanks to you i've got FOG working just fine on windows 7. now i am going to try imaging to muliple machines. Before i do though i was wondering what steps you do to get the drivers on the new image and how this relates to sysprep audit mode.

    If i have it clear i need to:
    Install windows 7.
    Boot into Audit mode.
    Install all drivers and software for that machine type.
    sysprep /shutdown
    upload the image to the Fog server.
    deploy the image to a new machine type.
    install/update any drivers
    sysprep /shutdown
    upload the image to the Fog server.
    and on and on it goes until all pcs are in that one image.

    Do i have to enter audit mode each time i deploy to a new pc type so i can add the drivers, or is this only needed first time around?
    Last edited by marlwoodadmin; 11th May 2011 at 02:23 PM.

  8. #38

    Join Date
    Mar 2011
    Location
    Bournemouth
    Posts
    280
    Thank Post
    16
    Thanked 74 Times in 64 Posts
    Rep Power
    21
    Quote Originally Posted by marlwoodadmin View Post
    Thanks for being so active on the forum ChrisMiles. Its been a great help reading your advice. Thanks to you i've got FOG working just fine on windows 7. now i am going to try imaging to muliple machines. Before i do though i was wondering what steps you do to get the drivers on the new image and how this relates to sysprep audit mode.

    If i have it clear i need to:
    Install windows 7.
    Boot into Audit mode.
    Install all drivers and software for that machine type.
    sysprep /shutdown
    upload the image to the Fog server.
    deploy the image to a new machine type.
    install/update any drivers
    sysprep /shutdown
    upload the image to the Fog server.
    and on and on it goes until all pcs are in that one image.

    Do i have to enter audit mode each time i deploy to a new pc type so i can add the drivers, or is this only needed first time around?
    Hi! You are quite welcome!

    Now, as for this list, I think there is some confusion. You don't need to use sysprep audit mode at all, just log into the computer as normal (as local or domain admin or some user with permission to add drivers), install drivers, re sysprep and upload:

    The list should look more like this:

    Install Windows 7
    Install all updates / drivers / software.
    sysprep /oobe /generalize /shutdown /unattend:unattend.xml (with your unattend.xml file in the c:\windows\system32\sysprep folder)
    Upload the image to the Fog server
    Deploy the image to a new machine type (and let it sysprep)
    Install all updates / drivers
    sysprep /oobe /generalize /shutdown /unattend:unattend.xml (with your unattend.xml file in the c:\windows\system32\sysprep folder)
    Upload the image to the Fog server

    and so on...

    I've never use audit mode for this process, although I'm not saying you cant

    Hope this helps

    I am considering writing up a step by step guide to setting up fog, installing and creating a windows 7 image in a domain environment. There is the a lot of cool stuff you can do to make it easier.

  9. Thanks to ChrisMiles from:

    sgagne (16th March 2012)

  10. #39

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Super. One less thing to do. I will start trying that this week and fingers crossed it should run smoothly.

    Thats brave of you doing documentation... I always mean to but never get around to it.

  11. #40
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    Rather than deploying to each hardware type, installing drivers and re-sysprep/upload again, we identify which drivers are required and add them into the driver store in main "clean" image with:

    pnputil –a <path to drivers>\*.inf

    We then sysprep and upload this to a deployable image. We're coming from XP ways of working where running sysprep against an image multiple times is generally accepted to be Not Good - it may not be a problem under W7 but this has worked for us so far.

    Chad

  12. #41

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Windows activation could be a problem if a machine is syspreped multiple time. See:
    Sysprep SkipRearm = 1

    Setting skiprearm is the solution for KMS activation (this is done in the unattend.xml)

  13. #42
    Chad's Avatar
    Join Date
    May 2007
    Location
    Elgin
    Posts
    74
    Thank Post
    5
    Thanked 20 Times in 19 Posts
    Rep Power
    18
    Quote Originally Posted by marlwoodadmin View Post
    Windows activation could be a problem if a machine is syspreped multiple time. See:
    Sysprep SkipRearm = 1

    Setting skiprearm is the solution for KMS activation (this is done in the unattend.xml)
    Thanks for that, I'll stick to our current way of having the deployed image sysprepped just the once.

  14. #43
    Modus's Avatar
    Join Date
    Jun 2011
    Posts
    18
    Thank Post
    0
    Thanked 4 Times in 4 Posts
    Rep Power
    7
    I'm using fog 0.29 and its been working great at 3 locations. We are still re-imaging with the windows xp but at some point windows 7 will be the next os for us, anyway i was wondering could i just use your unattended file you posted or should i try and make my own with the Windows System Image Manager?

  15. #44

    Join Date
    Jan 2008
    Location
    Bristol
    Posts
    11
    Thank Post
    2
    Thanked 1 Time in 1 Post
    Rep Power
    0
    You can use the one that ChrisMiles posted at the beginning of this thread.

  16. #45

    Join Date
    Oct 2011
    Location
    west bromwich
    Posts
    2
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by bart21 View Post
    Hi people

    We are using fog 0.29 with xp at the moment, We tried the 0.29 client with xp but it would not join to the domain so we use the 0.28 client and all is good.

    We are currently looking at windows 7, i have created an image and installed fog client 0.29. The hostname changes but no domain join happens, do i need netdom installed for windows 7. (i think i read somewhere that with fog client 0.29 netdom was not required.)

    Any ideas?

    Thanks for your help
    nick

    I have captured and deployed a windows 7 image and fog has been adding the machines to the domain. FOG uses the netdom.exe file. To get the netdom file:

    Install the Remote Server Administration Tools (RSAT).
    Go to Control Panel -> Programs and Features -> Turn Windows features on or off
    In the treeview, go to Remote Server Administration Tools -> Role Administration Tools -> AD DS and AD LDS Tools and select AD DS Tools. Click OK.

    Netdom will now be located in C:\Windows\System32. You will need to change the path to netdom in the config.ini file in the C:\Program Files\FOG\etc folder to point to C:\Windows\System32\netdom.exe

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

Similar Threads

  1. FOG, Windows XP and AD
    By wellscs in forum Windows
    Replies: 2
    Last Post: 14th December 2010, 09:32 AM
  2. Replies: 3
    Last Post: 29th September 2010, 11:44 PM
  3. Replies: 2
    Last Post: 18th August 2010, 07: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, 01:59 PM
  5. [Fog] FOG
    By CheeseDog in forum O/S Deployment
    Replies: 5
    Last Post: 3rd March 2009, 09: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
  •