I’ve been trying to manually update the oui.txt, copying the file into
/var/www/fog/management/other
is the import triggered by a cron, or will it only import after pressing the update button which fails due to it cannot download the file.
the FOG server is not connected to the internet, so it cannot download the oui.txt thus I have to do it manually.
cheers
For some reason, I cannot delete a computer from a group.
I’ve tried from group view, and also from the host view.
There is the “updated” message but nothing happens.
The host in mention is the first member of the group
on atleast UEFI based systems, the choice of booting from Local HDD makes the boot sequence hang.
So primary boot device cannot be the network.
On Win81 client / fog 1.2.0, during Sysprep (audit mode) I’ve installed the FOG-Service and activated hostname-change.
After putting the image into OOBE mode, and deploy the image, the hostnames of the deployed computers have the same name as the machine where the master image was created on. If I manually try and rename the other clients, FOG-Service makes sure that the hostname is changed back to what the Master is.
So hostname changer works… but gives the wrong name.
fog 1.2.0
I was trying to multicast to a group of computers. one of these computers was uploading.
When trying to make the multicast the first computers was added to the list, then the one uploading got an error.
The rest of the list wasn’t added.
i.e. pc3 is uploading pc1 - pc20 exists
only pc1 and pc2 was added to the list for deployment.
What is expected is an error message of PC3 occurs, but the rest is added.
I’ve recently installed a new Debian server with Fog 1.2.0, so the system is quite new.
I have some problems using the FOG Client.
Client computer runs Win81, and is basically just a clean install with some drivers, Firefox, Chrome, Hyper-V and .net Framework 3.5 + Updates.
My Goal is to run some Snap-ins after deployment.
The snap-ins are nothing more than batch scripts which needs to run as administrator.
Doubleclicking on the SFX snapin results in a success.
(it’s a self extracting archive made with “7-Zip SFX maker” that then calls the batch file, I also tried “SFXMaker”)
Lets take my most simple snap-in batch file as an example.
[CODE]powercfg -h off[/CODE]
For those who don’t know it it disables the hibernation, and removes the hibernation file.
The last entry of the log when deplying a non-sysprepped image (I can’t remember the exact log message but it was siimilar to):
"Running snap-in"
It just hangs there indefinately.
What I read somewhere is that some things won’t run properly when the FOG Service is running as a Local Service, and should run as the local Administrator.
I think I skipped testing this part on a non-sysprepped image, or I just can’t remember the outcome from last week.
So now I’m sys-prepping with a simple unattended file that activates the Administrator in the specialize phase + some other cosmetic things like setting user/company info, activation code etc. After OOBE runs the first time the client reboots and hangs indefinately. I found that it’s the FOG Client when it’s set to run as administrator. Running the FOG Client as Local Service, there are no issues in the boot sequence.
So here’s my dilemma, I can’t execute my batch scripts because the service isn’t running as administrator, I can’t run the service as administrator as it would render my image unusable.
I do have some little more advanced scripts, so even if I could deactivate hibernation and delete the hibernation file, instead of running the simple “powercfg -h off” I would still need to run batch scripts.
I did try to have Fog Service running as Local Service, then change it in specialize phase (4) in the unattended file (using WAIK)
[CODE]sc.exe config “FOG Service” obj= “.\Administrator” password= “somepassword”[/CODE]
I’d love to hear if anyone has any solutions for this.
I’m running my server in an environment with no internet access.
In my previous test setup for FOG 0.32 I removed the function that made the check of other online servers.
This is due to the fact that login takes ages (several minutes) as it waits for a timeout.
I’d like to see an option for turning this off.
my hacks of removing this feature are removed for every upgrade.
EDIT: Sorry probably wrong forum, perhaps this should have been posted in the bugs?
@Joseph
I guess you didn’t read/understand the problem, but your answer has no relevance for the subject.
Unfortunately it’s not an option for me to connect the FOG server to the internet.
it’s not critical for me though it’s nice to see the vendor ;-)
Perhaps a file upload form for manually updating would be available in the future?
Please see the attached file for full details, but answers are also below.
That sounds about right. Really weird.
I’m going to start making a sysprep machine for Win7 with some slight changes, most should look like the Win81 sysprep though. This is merely to see if the same server acts weird there or if it’s a Win81 problem.
[url="/_imported_xf_attachments/1/1370_unattended3-fog.xml.txt?:"]unattended3-fog.xml.txt[/url]