@Fernando-Gietz Okay I got it working. You guys are awesome keep it up!

@Fernando-Gietz Okay i’ll give it a try and report back once i get to the office today.

@Sebastian-Roth I was able to locate this but it’s kinda hard to tell where you are when you drill down into the role and you want to modify rules. Once I jump into the rules I can’t tell if i’m looking at the rules for just the role I created or if it’s all the default rules for all the roles, it feels like it should be some sort of bread crumb trail on the UI to indicate where you are at the time. Also I deleted the printers from the access control rules main menu as a test and it still shows up at the top menu bar, we are suppose to delete the access control rules we don’t want to show up right?

I hadn’t tried to do this sort of architecture before, I took the easy road and built a normal server at each site and manually replicated the image. Anyway I found the setting, thanks Tom.

I’ve setup a normal server using FOG 1.5.5 at our main office and storage nodes running FOG 1.5.5 at each of the remote sites that are few miles apart and I have an image replicating to the storage nodes. I’ve noticed that when imaging at the main office for example, it seems like the image may have been coming from one of the storage nodes instead of from the normal server that is located at the main office. I believe i saw this in tasks management under the working with node column, is there anything that can be done to make it so that client machines only image from the local server at the physical location?

@Sebastian-Roth I’m using 1.5.5 of FOG on all servers.

@Sebastian-Roth Nope. I didn’t know one existed, where is this located?

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