GreyFox Posted April 14, 2011 Posted April 14, 2011 It definitely works as long as the host configuration is set to Windows 7, however, I have only used this on 0.29 and 0.30. I'd recommend upgrading to 0.29. 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; http://www.edugeek.net/forums/o-s-deployment/68958-fog-windows-7-ntfs-resizable.html Thank you Grey Fox
ChrisMiles Posted April 14, 2011 Posted April 14, 2011 You are syspreping every time arn't you? It needs to be done on each machine, not just at the end. If so, does windows 7 install manually ok on the target machine? The only problem with this way of making images is that there is no opportunity to add disk controller drivers (ie F6 during install), and instead relies on windows having drivers available.
GreyFox Posted April 20, 2011 Posted April 20, 2011 I believe that's one of the points I missed! Sorry about the late response. My Fog Install decided to die - GUI was show white background, no graphics. Tried to install over the top, didn't fix, so uninstalled, then reinstalled and had issues with mysql password access etc. So ended up changing the hard drive, sticking Linux Mint 10 "Julia" on there (which is very nice!) and reinstalling Fog. We're all back and running now, plus download the older kernel so my machines actually work. Still got problems where my sysprep setup will work, captured, can deploy fine. Then update the image, all ready to go, run again, capture - sysprep fail! Thought it could be the fact I join the domain in order to install and setup one program. But just tried joining domain, restarted a few times then sysprepped and it worked! I have no idea now why it's failing. Fog seems to be ok now though. Need to try and remember what settings worked for the domain join though.
ChrisMiles Posted April 21, 2011 Posted April 21, 2011 Sysprep can fail to re-run if windows is not correctly activated each time before it is run. This is because windows only allows a maximum of 3 syspreps on an un activated copy of windows to prevent you using sysprep to bypass the grace period. Make sure your image is activating against KMS before attempting to re-sysprep.
GreyFox Posted May 4, 2011 Posted May 4, 2011 Hi again, it's been a while! We were having issues with our KMS host, so machines weren't automatically being activated. Turns out that it's still installed on 3 other machines (long story), so was getting confused. I have removed KMS from at least one of these, and removed all 3 from DNS, although it appears to keep coming back on. Will have to have another look at that. Anyway, we now have an image with drivers captured from several machines now! Thank you very much. However I'm still having issues adding a new machine to the domain - I don't know why. I've had loads of problems the past few weeks, 2 of these being Fog Server dying, then KMS issue. The next is that my machine and a my co-worker's have both stopped working, and can't speak to the domain. Ended up wiping and imaging with Fog - these both joined the domain absolutely fine - kept the name the same as when they were on XP. But most (I think all, but can't be sure) of the machines I've used for imaging have failed to join domain after sysprep. I think this is because they aren't already in the AD. This isn't an issue for the odd one or two machines, but when we come to replace a whole room, it could get interesting - plus it's not working quite how it should. I think it's down to the name for domain and administrator etc. Although I know the password is correct, got xxx\administrator and domain netbios name in. Any suggestions please? Thank you so much for your time, we are moving forward slowly but surely. kind regards GreyFox
Chad Posted May 4, 2011 Posted May 4, 2011 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
GreyFox Posted May 4, 2011 Posted May 4, 2011 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
Chad Posted May 4, 2011 Posted May 4, 2011 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!
GreyFox Posted May 6, 2011 Posted May 6, 2011 Hmm, getting a little bored of this now 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 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! [color="red"]('Unknown Error' Code: 1326[/color]) 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.
GreyFox Posted May 6, 2011 Posted May 6, 2011 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
Chad Posted May 6, 2011 Posted May 6, 2011 (edited) 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 Edited May 6, 2011 by Chad typo
marlwoodadmin Posted May 11, 2011 Posted May 11, 2011 (edited) 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? Edited May 11, 2011 by marlwoodadmin
ChrisMiles Posted May 11, 2011 Posted May 11, 2011 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. 1
marlwoodadmin Posted May 11, 2011 Posted May 11, 2011 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.
Chad Posted May 11, 2011 Posted May 11, 2011 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 \*.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
marlwoodadmin Posted May 11, 2011 Posted May 11, 2011 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)
Chad Posted May 11, 2011 Posted May 11, 2011 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.
Modus Posted June 3, 2011 Posted June 3, 2011 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?
marlwoodadmin Posted June 6, 2011 Posted June 6, 2011 You can use the one that ChrisMiles posted at the beginning of this thread.
saadi Posted October 30, 2011 Posted October 30, 2011 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
marlwoodadmin Posted October 31, 2011 Posted October 31, 2011 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. 1
saadi Posted October 31, 2011 Posted October 31, 2011 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.
marlwoodadmin Posted November 1, 2011 Posted November 1, 2011 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
mats Posted November 1, 2011 Posted November 1, 2011 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; http://www.edugeek.net/forums/o-s-deployment/68958-fog-windows-7-ntfs-resizable.html 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).
marlwoodadmin Posted November 1, 2011 Posted November 1, 2011 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!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now