It would be great if we had some sort of RBAC functionality built into fog, it doesn’t need to be anything complex. My use case is that I have central office IT staff that will have full access to fog, but I have computer technicians at schools that I only want to be able to image computers and not to have access to the web interface. Can this be done?

@george1421 Yeah it looks like by adding this to the xml file cscript /B C:\windows\system32_slmgr.vbs /ato resolved it on my machines. Thanks for the help.

@george1421 Can post a sanitized version of your unattended.xml file? I’m not sure what i should have in it to tell the workstation to find the kms server

I’m curious to know the answer to this, if you have a kms server in your environment do you have a product key in your unattend.xml file? or do you leave product key field blank or add something to the unattend.xml file to tell it to look for the KMS?

@Wayne-Workman Okay i’ll give that shot on monday

@Wayne-Workman I wouldn’t mind giving it a shot, where would the modifications need to take place?

When you have a single master and multi node fog architecture, does the master replicate to each of the storage nodes one at a time or does it replicate to all at the same time?

Is it possible to change the colors of the Bandwidth lines that represent different fog servers?

Noted. This makes sense.

I’m curious to know what you are doing to keep your computers updated with the new Windows 10 OS build updates as they come out. I believe with SCCM there are ways to update the computers without re-imaging them but how are you all doing this with FOG?

@sebastian-roth It’s working now.

I think I see where the issue is for me. I have created groups and associated the devices to groups, so the clients pull the settings like Active directory from the groups. In the domain name field I put DC=internal,DC=domain,DC=net when it should be internal.domain.net right?

Hi,

I am currently Running Version 1.4.4. I am looking for some help in trying to resolve the HostnameChanger Unknown Return Code: 9560 error, how is the resolved?

I am using the fields below
FOG_AD_DEFAULT_DOMAINNAME
FOG_AD_DEFAULT_USER

--------------------------------HostnameChanger-------------------------------

9/21/2017 11:31 AM Client-Info Client Version: 0.11.12
9/21/2017 11:31 AM Client-Info Client OS: Windows
9/21/2017 11:31 AM Client-Info Server Version: 1.4.4
9/21/2017 11:31 AM Middleware::Response Success
9/21/2017 11:31 AM HostnameChanger Checking Hostname
9/21/2017 11:31 AM HostnameChanger Hostname is correct
9/21/2017 11:31 AM HostnameChanger Attempting to join domain
9/21/2017 11:31 AM HostnameChanger Unknown Return Code: 9560

After I update the version of FOG I was able to image the 7240’s without issue. So issue is solved.

@george1421 Were you able to test this with a 7240 with 1.3.5 ?

@Tom-Elliott I was able to capture an image from a dell 6420 running windows 8.1 and deploy that out to about 50 targets so. I’m running on a physical server so if that RC isn’t stable then no.

It’s in the title they are dell 7240 latitude’s

Server

• FOG Version: 1.3.5
• OS: Ubuntu Server 16.10

Client

• Service Version:
• OS: windows 10

Description

How do I resolved the error below? I tried acpi=off nomodeset in the host kernel arguments but that didn’t work
Click here to see the error when I try to fog a dell 7240 laptop

From what i can tell from testing is that this seems to be an issue only when using ubuntu 14.04, i’m going back 12.04 LTS because it doesn’t seem like its an issue on that version.

[quote=“domii666, post: 38175, member: 24204”]sql is running?[/quote]

I’ve searched and tried a few things but none of them help

[url]https://www.google.com/search?q=Database+Schema+Installer+%2F+Updater&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&channel=rcs#q=Database+Schema+Installer+%2F+Updater+site%3Afogproject.org&rls=org.mozilla:en-US:official&channel=rcs[/url]