Posts made by adukes40

Yea i know its way out. Neat to hear they are considering something like that tho. Shame to hear about DameWare. I read a lot of good things about it, but like i said, just getting ideas, and opinions before we start moving forward. Not happening any time soon, but still good to try and get the ducks in a row ahead of time.

Is Guac more like a 2.0 feature?

Just wondering what you all use for remote control to support to end users. I have seen some ideas, such as Kaseya, LabTech, DameWare. Trying to get a feel what others are using, as most of us are in the K12 world.

@JMacavali I believe you just disable secure boot, and make sure you choose to use Legacy ROMs. We do that on anything newer than a OptiPlex 790 (I believe) in our environment, I have 5040’s and We do not use UEFI anything yet.

@jkepple2003 are you typing just the IP or <IP>/fog/management as the url?

The scripts I use do that. They get the model, and architecture, then using that pulls the needed drivers for the machine. All automated.

Everything currently runs off of eth0. When Imaging is being done at the masternode, my connection to the GUI suffers. How easy is it to move management to eth1 and leave all the nodes pointing to eth0?

@george1421 Just got the new master pushed up, and the M.2’s are now working great.

@george1421 Awesome, thanks again George, I will start working on that now.

We have a whole lab I threw together an image for using the actual 5040. But this image is done from the VM. The two updates you mention I highly doubt are installed. I was just starting to read on a couple KBs that address this. Could you confirm that the updates are KB2990941 and KB3087873? If so I will down load them, and install them onto the VM.
Also for my own information, Win10 has native support for M.2 correct? Just not 7?

We have some OptiPlex 5040’s with M.2 Sata’s. After FOG pushes the image, and Windows tries to boot to do its mini setup, it places the 2 Microsoft dots on the screen like it is about to load, then reboots. Then just does a constant boot loop. The SSD’s are PM951 Samsungs.

Has anyone else seen this happen?

@MRCUR Understood. but it is old client on newer version of FOG. During our last hangout this got brought up. Tom and Joe work closely together on making sure FOG and the client work together. It was suggested to me that I update and when I did it all worked perfectly. I am assuming that something changed between the 0.10.6 client and 0.11.2 client with the coding in FOG since those releases that does not work with the older clients.

Joe would be able to explain it more, but I would think updating everything to the newer one would do the trick.

I can’t tell you as much in the technical sense, but last week when I updated to 8255 I was still running the 0.10.6 verison of the client and things were breaking. After updating it to 0.11.2, everything worked like magic. I would suggest updating the client to the the new 0.11.2 version.

@Tom-Elliott Did i read somewhere not too long ago that the svn way is going away??? We would have to use git?

I got tired of typing that lol. I use a folder called foginstall to hold the files so I just hit the up arrow and run this command:

cd /opt/foginstall; svn up; cd /opt/foginstall/bin; ./installfog.sh -y

@Wayne-Workman Would the command for chown on the bg.png be the fog:root? (for clarification)

chown -R fog:root <Path to file>???

https://www.reddit.com/r/sysadmin/comments/4q21g9/snappy_driver_installer_development_has_stopped/?sort=new&compact=true

@Wayne-Workman Anytime. I would just need to try to clear my schedule if I needed to.

just checked back on my image, having the fog log set to the default root of C, doesn’t give the windows prompt about the Program file. I do believe, Wayne, the Program file is still showing as of 0.11.2 on update.

I turned on the auto updater for the client, and it updated from 10.6 to 11.2, it would leave the Program file there. I also had it set to do the install directory and not the root of

I had that as well. It seems if you told the client to put the log in the install directory, it still creates the program file in C:. I just placed the new client on my master images over the weekend, and told the log to install to C:. I am imaging right now to test this.

It has been recommended if this does occur to have a script delete the additional “Program” file in the root of C:. I will also comment back to verify changing the location from the install directory to the default root of C causes the extra file to disappear.