Not sure about the disk information, but the stuff on the login screen reaches out to the main FOG hosting servers to get the info… do you have any firewall rules that might affect this on your FOG box?
Latest posts made by John Deery
-
RE: Something is wrong with my install... screen shots attached
-
RE: "Reinstall my computer" for users
Sure, it’s possible. What you would need to do is look in to the FOG code to see how, when you tell a machine to reimage on next boot, it calls and sets up the database. Then you would just either write a similar script in your portal where it grabs the current machine name of the user logged in and directly updates the database or you could make a remote request (ajax) to the fog manager interface. Either way it’s possible.
I think the real question, though, is why do you want your users to have this ability? If you set all of their computers to boot to PXE as the first option then when they need a reinstall you (or whoever on your tech crew) could just trigger it from the web interface and then tell them to restart. The main concern would be bandwidth usage if a lot of people decide to trigger a reinstall at the same time and the waiting queue unless you change it from the default of 10
-
RE: Integrate Windows Authentication in FOG
The code for it isn’t all that bad and I have a small working version of AD integration. It does require the apache ldap module to be installed but otherwise it just does a quick anonymous bind to the AD to look up the name and, if found, tries another bind with the name and password. Of course the first check can be taken out since not everyone will allow anonymous binding to their AD.
I think BryceZ has the right of it, too, that after doing the check, certain information will need to be passed on to FOG to allow for the local access features. Moodle does a really nice job of this, so that may be somewhere to look.
I’m guessing that with the .33 framework that this all could be achieved via a plugin instead of putting it into the core of the program.
-
RE: Bugs in FOG 0.33
Found a visual bug on the login form. If you switch languages, the names and fields would get all out-of-wack. The diff file I have attached should fix the issue (tested in the latest FF, Chrome and IE 9), just add a .diff to the end if you’re using svn.
[url=“/_imported_xf_attachments/0/216_fog.css?:”]fog.css[/url]
-
RE: Windows 7 Deployment FOG- SAD2 Driver tool
Something I noticed looking at the DP_Install_Tool.cmd… the line
[CODE]Start /wait /separate /high “” “%cur%\bin\un7zip.exe” “%cur%\bin\dpinst64.7z” %SystemDrive%\D[/CODE]
Looking at the SAD2 structure, the folders are \bin[32 or 64]\dpinst.7z
Should this be updated in the DP_Install_Tool.cmd example? Or maybe just a note to put the modified commands for the RemoveD.cmd at the bottom of the DP_Install_Tool.cmd that is provided with the release?
-
RE: Windows 7 Deployment FOG- SAD2 Driver tool
[quote=“andyroo54, post: 7825, member: 267”]Yeah mine does this to. For me it isn’t a problem as we use our own anti virus etc. Once a machine is imaged it gets another 30 days to activate it.
I suppose that’s one way… you could deploy it to another virtual machine, then put that machine back into sysprep, and re add your unattend xml etc.
Perhaps you could also change the date somehow in the ‘bios’ of the virtual machine.[/quote]
I decided to just reinstall… tied in with ninite, it goes pretty quickly. Thanks for the amazing guide, btw!
-
AD Joiner modification
Under the old site, someone had posted a change to the AD joiner that did a check for if the computer was already an AD member, and it either unjoined and then rejoined or did a merge… I forget the specifics, but I was wondering if anyone had the code/tutorial on how to do this, as we’re going to be reimaging a large amount of computers and trying to track the AD objects is going to be a hassle.
Thanks!
-
RE: Windows 7 Deployment FOG- SAD2 Driver tool
Hey all,
So I was following the guide and I have set up my Win 7 VM (using VirtualBox) but I guess I went over my initial 30 days, so now I’m in non-genuine mode. I never installed Security Essentials, so I’d like to do that, but I can’t until I activate. What should I do? And even using the VM snapshot method, won’t it always jump back to non-genuine after the 30 day non-activated period is up?
-
RE: Odd one: one image not changing hostname or joining after imaging
Little late to the party, but I am also seeing this type of issue on our main Windows XP image. After sysprep is done, fog services will not fire. Fog.log shows the following:
[CODE]
8/8/2012 9:40 AM FOG::GreenFog Starting green fog…
8/8/2012 9:40 AM FOG::GreenFog Attempting to connect to fog server…
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::SnapinClient Sleeping for 497 seconds.
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::AutoLogOut Unable to continue, MAC is null!
8/8/2012 9:41 AM FOG::UserTracker Unable to determine MAC address, exiting…
8/8/2012 9:41 AM FOG::TaskReboot Attempting to connect to fog server…
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::HostnameChanger Host name was not found in the database.
[/CODE]A temporary solution I have is to tell sysprep to run the net stop “Fog Service” and net start “Fog Service” commands on first login after the imaging is done, but this still fails when trying to join the domain. So my current solution would be to add a batch script that runs any time the computer logs in to restart the service.
-
Update for index.php?node=about&sub=kernel (css)
I think this fits here (if not mods, let me know where).
I have having difficulty viewing the different Kernels on index.php?node=about&sub=kernel, so I threw in some CSS and figured I would share. I placed it at the bottom of my Global.css.
With .33 it will probably be styled, but until then, enjoy:
[CODE]* Kernel Update Page */
.kernel { border-bottom: 1px solid black; }
.kernel .kernelTitle { font-weight: bold; margin: 0; padding: 0; }
.kernel .kernelDetail { margin: 0 0 0 10pt; }
.kernel .downloadKContainer { margin: 0; padding: 0 0 0 10pt; }
[/CODE]In the future I would like to see (or I’ll create) a way to track which kernels have been downloaded and to which file name so that users in the system aren’t downloading the same ones over and over again. Unless, of course, this already exists and I’m blind