• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Dekar
    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 6
    • Best 0
    • Controversial 0
    • Groups 0

    Dekar

    @Dekar

    0
    Reputation
    214
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Dekar Unfollow Follow

    Latest posts made by Dekar

    • RE: Fog Domain join issues

      My real goal with sysprepping was to have an image that is capable of being deployed to multiple computer models. What I was hoping to do (and maybe this is a flawed thought process) was to have an image that is sysprepped (to remove hardware unique drivers, add in activation keys, ect) so I could deploy it to the 20 different computer models I have. Then for each model I intended to install any missing/needed drivers and upload an image to fog for that model with drivers in-tact so when I deploy it, it is ready to go without being touched. Then I would end up with the following:

      1. “golden” sysprepped image that I can use for all computer models - current and future (always have an image ready)
      2. A “complete package” image (not sysprepped) for each model of computer I have (HP Elitebook 8440, HP Compaq DC7900, HP Elitebook 850, ect) this also allows me to have unique software added to these images so they are customized for the location (some software on these is as big as 50GB and does not work for group policy or snap-ins).

      So really i’m not deploying sysprep to install drivers, in fact i’m doing quite the opposite. Really all the sysprepped image is for is to prevent having to pop a windows 8 disc into every model of computer and build an image from scratch. It gives me a good base that only needs drivers and miscellaneous software.

      Does this sound like a reasonable approach, or am I going about this all wrong?

      posted in FOG Problems
      D
      Dekar
    • RE: Fog Domain join issues

      After some more tinkering I seem to have a little more information that might help to narrow this down.

      1. After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
      2. If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
      3. I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)

      Hopefully this helps to narrow the problem down. I’ll continue to look into it.

      Thanks

      posted in FOG Problems
      D
      Dekar
    • RE: Fog Domain join issues

      I have tried it both with the domain name and without the domain name with the same result. Currently I have removed the domain name and am just using the username. I will keep troubleshooting and let you know if I come up with anything.

      Thanks for the reply!!

      posted in FOG Problems
      D
      Dekar
    • Fog Domain join issues

      Hello all,

      I have recently run into serious issues getting fog service to rename/join my domain.

      I have tried everything I can think of to fix it… Reinstalled fog service, rebuilt my images, checked all settings in fog including my credentials and host settings, ect. I am beginning to believe it may be related to my domain controller/DNS but I cant be sure. This is a newly updated fog server to 1.0.1 and I have never had issues with fog service before. One thing that is relatively new is that I have started sysprepping. Hoping for some advice. It appears to change the NetBIOS name but not the actual host name (see image). It also see’s the username as the host it should have changed the name to, but the actual host name remains unchanged.

      The hostname of my image (which should be changed to the hostname listed in fog) is CHSCLASSHHE8Q8
      The hostname of THIS host that was imaged (which is not being properly renamed) is CHSCLASSHHE93S

      Here is some gathered information:

      6/3/2014 2:16 PM FOG::DirCleaner Attempting to connect to fog server…
      6/3/2014 2:16 PM FOG::DirCleaner Module is disabled on this host.
      6/3/2014 2:16 PM FOG::GreenFog Starting green fog…
      6/3/2014 2:16 PM FOG::GreenFog Attempting to connect to fog server…
      6/3/2014 2:16 PM FOG::GreenFog Module is active…
      6/3/2014 2:16 PM FOG::GreenFog No actions were found.
      6/3/2014 2:16 PM FOG::GreenFog No tasks found after validation!
      6/3/2014 2:17 PM FOG::MODDebug Reading config settings…
      6/3/2014 2:17 PM FOG::MODDebug Reading of config settings passed.
      6/3/2014 2:17 PM FOG::MODDebug Starting Core processing…
      6/3/2014 2:17 PM FOG::MODDebug Operating System ID: 6
      6/3/2014 2:17 PM FOG::MODDebug Operating System Minor: 2
      6/3/2014 2:17 PM FOG::MODDebug MAC ID 0 00:24:81:98:19:04
      6/3/2014 2:17 PM FOG::MODDebug MAC POST String: 00:24:81:98:19:04
      6/3/2014 2:17 PM FOG::MODDebug A user is currently logged in
      6/3/2014 2:17 PM FOG::MODDebug Username: [B]CHSCLASSHHE93S\RRPSadmin[/B]
      6/3/2014 2:17 PM FOG::MODDebug Hostname: [B]CHSCLASSHHE93S[/B]
      6/3/2014 2:17 PM FOG::MODDebug Attempting to open connect to: [url]http://10.64.100.64/fog/service/debug.php[/url]
      6/3/2014 2:17 PM FOG::MODDebug Server responded with: Hello FOG Client
      6/3/2014 2:17 PM FOG::MODDebug Module has finished work and will now exit.
      6/3/2014 2:18 PM Service Stop requested
      6/3/2014 2:18 PM FOG::AutoLogOut Shutdown complete
      6/3/2014 2:18 PM FOG::ClientUpdater Shutdown complete
      6/3/2014 2:18 PM FOG::DirCleaner Shutdown complete
      6/3/2014 2:18 PM FOG::DisplayManager Shutdown complete
      6/3/2014 2:18 PM FOG::GreenFog Shutdown complete
      6/3/2014 2:18 PM FOG::GUIWatcher Stopping…
      6/3/2014 2:18 PM FOG::HostnameChanger Shutdown complete
      6/3/2014 2:18 PM FOG::HostRegister Shutdown complete
      6/3/2014 2:18 PM FOG::MODDebug Shutdown complete
      6/3/2014 2:18 PM FOG::PrinterManager Shuting down
      6/3/2014 2:18 PM FOG::SnapinClient Shutdown complete
      6/3/2014 2:18 PM FOG::TaskReboot Stopping…
      6/3/2014 2:18 PM FOG::UserCleanup Shutdown complete
      6/3/2014 2:18 PM FOG::UserTracker Shutdown complete
      6/3/2014 2:18 PM FOG Service Engine Version: 3
      6/3/2014 2:18 PM Starting all sub processes
      6/3/2014 2:18 PM 14 modules loaded
      6/3/2014 2:18 PM * Starting FOG.AutoLogOut
      6/3/2014 2:18 PM * Starting FOG.SnapinClient
      6/3/2014 2:18 PM FOG::AutoLogOut Starting process…
      6/3/2014 2:18 PM FOG::ClientUpdater Starting client update process…
      6/3/2014 2:18 PM FOG::ClientUpdater Sleeping for 224 seconds.
      6/3/2014 2:18 PM * Starting FOG.DirCleaner
      6/3/2014 2:18 PM * Starting FOG.DisplayManager
      6/3/2014 2:18 PM FOG::DirCleaner Sleeping for 36 seconds.
      6/3/2014 2:18 PM * Starting FOG.GreenFog
      6/3/2014 2:18 PM FOG::DisplayManager Starting display manager process…
      6/3/2014 2:18 PM * Starting FOG.GUIWatcher
      6/3/2014 2:18 PM FOG::GUIWatcher Starting GUI Watcher…
      6/3/2014 2:18 PM * Starting FOG.HostNameChanger
      6/3/2014 2:18 PM FOG::GreenFog Sleeping for 47 seconds.
      6/3/2014 2:18 PM * Starting FOG.HostRegister
      6/3/2014 2:18 PM FOG::HostnameChanger Starting hostname change process…
      6/3/2014 2:18 PM FOG::HostRegister Starting host registration process…
      6/3/2014 2:18 PM FOG::HostnameChanger Yielding to other subservices for 9 seconds.
      6/3/2014 2:18 PM * Starting FOG.MODDebug
      6/3/2014 2:18 PM * Starting FOG.PrinterManager
      6/3/2014 2:18 PM FOG::MODDebug Start Called
      6/3/2014 2:18 PM FOG::MODDebug Sleeping for 100 Seconds
      6/3/2014 2:18 PM * Starting FOG.SnapinClient
      6/3/2014 2:18 PM FOG::PrinterManager Starting interprocess communication process…
      6/3/2014 2:18 PM * Starting FOG.TaskReboot
      6/3/2014 2:18 PM FOG::TaskReboot Taskreboot in lazy mode.
      6/3/2014 2:18 PM FOG::TaskReboot Starting Task Reboot…
      6/3/2014 2:18 PM FOG::SnapinClient Starting snapin client process…
      6/3/2014 2:18 PM FOG::PrinterManager interprocess comm startup: OK
      6/3/2014 2:18 PM * Starting FOG.UserCleanup
      6/3/2014 2:18 PM * Starting FOG.UserTracker
      6/3/2014 2:18 PM FOG::UserCleanup Sleeping for 13 seconds.
      6/3/2014 2:18 PM FOG::UserTracker Starting user tracking process…
      6/3/2014 2:18 PM FOG::SnapinClient Sleeping for 421 seconds.
      6/3/2014 2:18 PM FOG::HostRegister Exiting because only 1 mac address was found.
      6/3/2014 2:18 PM FOG::DisplayManager Attempting to connect to fog server…
      6/3/2014 2:18 PM FOG::PrinterManager Attempting to connect to fog server…
      6/3/2014 2:18 PM FOG::UserTracker Attempting to connect to fog server…
      6/3/2014 2:18 PM FOG::DisplayManager Module is disabled globally on the FOG Server.
      6/3/2014 2:18 PM FOG::AutoLogOut Module is active…
      6/3/2014 2:18 PM FOG::PrinterManager Module is active…
      6/3/2014 2:18 PM FOG::PrinterManager Starting printer manager…
      6/3/2014 2:18 PM FOG::PrinterManager Yielding to other services for 34 seconds.
      6/3/2014 2:18 PM FOG::UserTracker Module is active…
      6/3/2014 2:18 PM FOG::AutoLogOut Timeout value is Zero, disabling module.
      6/3/2014 2:18 PM FOG::AutoLogOut c:\program files\fog\images\alo-bg.jpg
      6/3/2014 2:18 PM FOG::AutoLogOut at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
      at FOG.AutoLogOut.doWork()
      6/3/2014 2:19 PM FOG::HostnameChanger Attempting to connect to fog server…
      6/3/2014 2:19 PM FOG::HostnameChanger Module is active…
      6/3/2014 2:19 PM FOG::HostnameChanger AD mode requested, confirming settings.
      6/3/2014 2:19 PM FOG::HostnameChanger Hostname is up to date
      6/3/2014 2:19 PM FOG::HostnameChanger Attempting to join domain if not already a member…
      6/3/2014 2:19 PM FOG::UserCleanup Starting user cleanup process…
      6/3/2014 2:19 PM FOG::UserCleanup Attempting to connect to fog server…
      6/3/2014 2:19 PM FOG::UserCleanup Module is disabled globally on the FOG Server, exiting.
      [B][COLOR=#000000] 6/3/2014 2:19 PM FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 2725) [/COLOR][/B]
      6/3/2014 2:19 PM FOG::PrinterManager Management level = 0
      6/3/2014 2:19 PM FOG::PrinterManager This host is set to NO MANAGEMENT, we will exit now.
      6/3/2014 2:19 PM FOG::PrinterManager Major printing operations complete, moving to tracking mode.
      6/3/2014 2:19 PM FOG::DirCleaner Starting directory cleaning process…
      6/3/2014 2:19 PM FOG::DirCleaner Attempting to connect to fog server…
      6/3/2014 2:19 PM FOG::DirCleaner Module is disabled on this host.
      6/3/2014 2:19 PM FOG::PrinterManager New user detected: [B]CHSCLASSHHE93S\RRPSadmin[/B]
      6/3/2014 2:19 PM FOG::PrinterManager Waiting for tray to load…
      6/3/2014 2:19 PM FOG::GreenFog Starting green fog…
      6/3/2014 2:19 PM FOG::GreenFog Attempting to connect to fog server…
      6/3/2014 2:19 PM FOG::GreenFog Module is active…
      6/3/2014 2:19 PM FOG::GreenFog No actions were found.
      6/3/2014 2:19 PM FOG::GreenFog No tasks found after validation!
      6/3/2014 2:20 PM FOG::MODDebug Reading config settings…
      6/3/2014 2:20 PM FOG::MODDebug Reading of config settings passed.
      6/3/2014 2:20 PM FOG::MODDebug Starting Core processing…
      6/3/2014 2:20 PM FOG::MODDebug Operating System ID: 6
      6/3/2014 2:20 PM FOG::MODDebug Operating System Minor: 2
      6/3/2014 2:20 PM FOG::MODDebug MAC ID 0 00:24:81:98:19:04
      6/3/2014 2:20 PM FOG::MODDebug MAC POST String: 00:24:81:98:19:04
      6/3/2014 2:20 PM FOG::MODDebug A user is currently logged in
      6/3/2014 2:20 PM FOG::MODDebug Username: [B]CHSCLASSHHE93S\RRPSadmin[/B]
      6/3/2014 2:20 PM FOG::MODDebug Hostname: [B]CHSCLASSHHE93S[/B]
      6/3/2014 2:20 PM FOG::MODDebug Attempting to open connect to: [url]http://10.64.100.64/fog/service/debug.php[/url]
      6/3/2014 2:20 PM FOG::MODDebug Server responded with: Hello FOG Client
      6/3/2014 2:20 PM FOG::MODDebug Module has finished work and will now exit.
      6/3/2014 2:22 PM FOG::ClientUpdater Attempting to connect to fog server…
      6/3/2014 2:22 PM FOG::ClientUpdater Module is active…

      When I try to MANUALLY add this computer the domain after fog is unsuccessful in doing so, I get this error:
      This only happens after I image with fog, I can add other machines to my domain manually with no issues.
      [ATTACH=full]895[/ATTACH]
      [ATTACH=full]896[/ATTACH]

      [url=“/_imported_xf_attachments/0/895_domain join error.PNG?:”]domain join error.PNG[/url][url=“/_imported_xf_attachments/0/896_netbios.PNG?:”]netbios.PNG[/url]

      posted in FOG Problems
      D
      Dekar
    • RE: Issue with image creation on brand new HP machines - please help!

      After messing around for a while I was able to get the EliteBook to pull an image successfully. I am not 100% sure how I fixed it (or why it worked). All I did was format the HDD using the windows 7 disc and allow it to use its default settings when creating the new partition (including the system files partition). I created the image as a multiple partition non re-sizable image in fog and pulled it and it just worked. I deployed it successfully as well.

      As for the ProDesk, I am still working on it. I don’t know how or why the hard drive became GPT formatted (it’s only a 500GB hard drive) but it did. I pulled it and put it into a working machine as a 2nd hard drive and tried to re format it as MBR, but windows would not allow it. I used partition software to unallocate the space and cleaned it. I was then able to reformat the drive as MBR. I have not yet tried to pull an image into fog with it, more to come.

      posted in FOG Problems
      D
      Dekar
    • Issue with image creation on brand new HP machines - please help!

      Hello,

      I have been using fog for a relatively short period of time but have had much success. I work at a high school and we have thousands of computers all working on fog with 10+ different machines with working images.

      I have recently purchased multiple new computers to build new computer labs. They are all the latest and greatest HP has to offer. I was unable to find a kernel that would work with these new computers (HP Elitebook 850 laptops and HP ProDesk 600G1 desktops). Because I could not find a working kernel, I decided to try to create a custom kernel to get these to work. I was relatively successful as I was able to get the Elitebook 850 to now start the process of pulling a fog image as it now seems to recognize network drivers. This computer model is currently my focus.

      This is what I now run in to:

      1. The image will begin to pull, but it attempts to pull the partition size as the entire 465GB of usable space on the hard drive. If I would allow it to continue it seems as if it would pull a 465GB image. This seems backwards, almost as if it is trying to pull the empty space as an image instead of the operating system. I have tried a single partition and multiple partition image, both have the same result. Any advice would be appreciated.

      2. The HP ProDesk will not properly function in fog at all - it gives me this a few seconds after the fog network boot UI shows up “GPT-formatted disk - press control alt delete to reboot”. When I received these computers I used the windows disk that came with to format the hard drive and installed windows from scratch. I am not super familiar with disk formatting types and what works best in fog, but I was surprised to see this. Any advice would be appreciated.

      The kernel I used to make the custom fog kernel was the latest kernel from [url=“http://www.kernel.org”]www.kernel.org[/url]

      posted in FOG Problems
      D
      Dekar