And I don’t have time to re-image!

@Wayne-Workman I’m seeing that. LOL! Too bad my hands are still tied for doing GPO work… My colleague is too scared to mess with it and won’t give me privileges. I love my job. LOL!

Looks like installing them the old fashioned way is what I’ll have to do.

@Wayne-Workman I have a lab that was having issues receiving pushed printers. I figured it was an issue with the Client. I was going to update the client up to current. So that’s where I"m at.

@Wayne-Workman

FOG Client Tray Ver 0.1
Released Under GPL Version 3

Will this client automatically update to current if the MSI is uploaded to client service updater on the server?

If so, how long does it take to update on the clients?

I’m assuming this is the easiest solution to updating our legacy clients short of uninstalling and re-installing clients on each host.

Thanks!

Cheers!

Joe

@Wayne-Workman

Glad to see it’s not completely unusual. I’ll try that Monday and see if I can’t resolve it. Thanks!

Cheers,

Joe

@Wayne-Workman
I noticed that one of my machines on our network is getting the same name in FOG PXE as another machine that has already been fogged. The identical named machine was never on the network prior. When I booted it up to FOG PXE it was already named the same name as another host. Is it possible for the machines to have identical MAC addresses? If so what’s the best solution?

Thanks!

Cheers,

Joe

@Wayne-Workman Thanks! That worked!

@Wayne-Workman Hmmmm. I don’t see pending MAC addresses anyplace on this host.

I see this in the FOG log file on the host.

--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 8/25/2016 4:20 PM Client-Info Client Version: 0.11.5
 8/25/2016 4:20 PM Client-Info Client OS:      Windows
 8/25/2016 4:20 PM Client-Info Server Version: 16
 8/25/2016 4:20 PM Middleware::Response ERROR: Unable to get subsection
 8/25/2016 4:20 PM Middleware::Response ERROR: Object reference not set to an instance of an object.

------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 8/25/2016 4:20 PM Client-Info Client Version: 0.11.5
 8/25/2016 4:20 PM Client-Info Client OS:      Windows
 8/25/2016 4:20 PM Client-Info Server Version: 16
 8/25/2016 4:20 PM Middleware::Response ERROR: Unable to get subsection
 8/25/2016 4:20 PM Middleware::Response ERROR: Object reference not set to an instance of an object.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 8/25/2016 4:20 PM Client-Info Client Version: 0.11.5
 8/25/2016 4:20 PM Client-Info Client OS:      Windows
 8/25/2016 4:20 PM Client-Info Server Version: 16
 8/25/2016 4:20 PM Middleware::Response ERROR: Unable to get subsection
 8/25/2016 4:20 PM Middleware::Response ERROR: Object reference not set to an instance of an object.
 8/25/2016 4:20 PM Middleware::Communication URL: http://172.16.1.17/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 8/25/2016 4:20 PM Middleware::Response Success
 8/25/2016 4:20 PM Service Sleeping for 147 seconds```

I’m assuming you just set host to ignore mac address for the fog client.

Cheers!

Joe

Are their any known issues with the FOG client on laptops? I have imaged several laptops using the ethernet card but the majority of our users use them on our wireless network. Both the wired and wireless networks in the school are both on the same domain. So I’m assuming that the FOG client should react in the same manor. I would like to utilize the printer manager on these devices and I’m hoping I can do so still.

Any suggestions would be helpful. Thanks!

Cheers!,

Joe

@Wayne-Workman I wish that was the case. In this particular instance, this was the only image going. I just had a one off image to do.

@Wayne-Workman Thanks!

I’ll see if I can’t watch one finish. The funny thing is the most recent one rolled over into this mess and on the second iteration of the image process, it finished. Ugh!

I’ll see if I can replicate this and then I’ll debug.

Running Version RC-8

I’ve noticed a few imaging tasks lately have never finished. They will go through the imaging process and then at the end of the task, reboot and start over. Please let me know what FOG logs I need to post or if you have any ideas on how to fix this. I know the images have worked in the past so I’m not sure what changed.

Thanks!

Cheers!

Joe

@Wayne-Workman

Well I’ve discovered lots…

This post on Spiceworks says tons!!
https://community.spiceworks.com/topic/504924-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed?page=1

Basically it’s caused by NOT sysprepping machines. Hence the reason you’ve never seen it before… This lab was NOT sysprepped… Ugh!!

That said, the easy fix is to run the following powershell command using Powershell 3.0. Which in my case I had to download…

reset-computermachinepassword

Run this locally and it will do the job! Now… In my case it did not! I’m guessing because my PID was not unique because of the lack of Sysprep… The DC does not recognize the machine as being unique. The only work around aside from re-imaging the entire lab, is to go in and rejoin the domain by changing from mydomain.com to mydomain. This seems to do the trick with a reboot. I could have FOG do it but it’s the same amount of steps…

Thanks!

I can’t wait to fix our DC let me tell you!

Cheers,

Joe

@Wayne-Workman I haven’t yet!! But I’m still forging away!

@Wayne-Workman

So I was trying to debug a script this evening and discovered this…(Look at screenshot below) I find it scary and comical at the same time. All I have to say is “WOW”! This mess is more screwed up than I thought!!!

For those looking for a good script to remove computers from your domain from one single script, look no further…

Check this link out – >
http://blog.the-it-blog.co.uk/2013/08/01/how-to-remove-a-pc-from-a-domain-and-join-it-using-powershell/

I will warn you, I had some bugs to work through. Most will be very simple for you to figure out.

What killed my script was what’s pictured below. When you have ip addresses on your network that represent several different machine names you have bigger issues… UGH!

I did find several variations of this script. Most were written to be ran on your local admin PC. This one is nice because you can create a CSV file of PC names to be removed. Their is also a script on this page to re-add the machines. Both are handy to have!

Anyhow, check out my misfortune. LOL!

@Wayne-Workman The command seems simple but I can’t figure it out for the life of me. I seriously need to study up on scripting let me tell you.

The command is remove-computer. But I can’t get the syntax right.

@Wayne-Workman Will do! I’ve been fighting with it all afternoon. Working on it from home right now. LOL!

@Wayne-Workman Sadly I understand what you’re saying. The funny thing is, when I was doing a search for a script, I found some other poor soul who experiences this same issue. I’m betting he has things all messed up, much like we do here. It’ll change here though. Give me 6 more months and I’ll get this place turned around. We only barely have 400 machines. Small potatoes in the grand scheme of things!

Thanks for the support!

@Wayne-Workman LMAO! I’m working on it! It’s been a tough road though. Discovered a lot of things that weren’t very Kosher. One thing at a time. At least our images have been sysprepped and KMS keys installed. Oh and I shouldn’t forget FOG! Boy what would I do without FOG?! I’m moving up in the world!

Thanks again!