Best posts made by Wayne Workman

@boeleke edit the /opt/fog/.fogsettings file to have the right IPs in it, then re-run the installer and see if it works. There are some fields that are not in the DB or editable from the web interface that the installer sets an IP address in.

@mr626 said in Windows 10- moving from 1511 to 1607 in audit mode?:

Or do I need to recreate my master image with a 1607 build Windows 10 from scratch?

That is exactly what I was thinking before I read this last line in your post. Just start fresh. It doesn’t take too long to do if you have a list of the software and general configuration needed. This would generally take a morning’s worth of work to accomplish.

This question comes up from time to time on the forums.

Let me first say that I don’t sysprep. Everyone keeps telling me I need to, but I am doing just fine without it and I take care of 20+ models and have been involved with the imaging of over 4,000 individual computers with FOG, and without sysprep. This sort of endevor wouldn’t be possible without the FOG Client (kudos to @Joe-Schmitt for creating such an amazing tool), and without extensive FOG know-how. FOG can automate basically everything you need done post-imaging. Without FOG (or a tool with comparable features), you’d need a massive workforce to do that sort of endeavor, or a hodge-podge of software deployment methods. With fog, a one to two person team could do it - if you’re only talking about the imaging and configuration process.

You don’t have to use sys-prep. But there are environments and demands were it would be very helpful. There’s also environments and demands where it’d just be an un-needed extra step.

If you use an internal WSUS server, you might want to sysprep because there have been issues reported on the internet about duplicate clients in WSUS that causes problems. I’ve used WSUS without sysprep with Win7 Pro and have not had this issue, and WSUS got the job done.

Not sys-prepping has zero negative effect on the domain-joining process. If it did, I would absolutely have known about 6 years ago when I first started imaging using Norton Ghost. I am responsible for several large domains, none of the computers joined to them are sys-prepped and we don’t have issues concerning it.

If you use an internal KMS server for activation (and not MAK keys), you might want to sysprep or you will have an issue reaching the initial threshold for activating Windows and Office and such. The issue with this is that when each individual host makes a request to the KMS box for activation, it sends with it it’s SID too. For Windows and Office, there’s a unique request threshhold that must be reached before the KMS box will actually activate anything. I don’t sysprep and I have heavily used KMS at work. I got around the threshold issue by using a “charger” program that I found online, this application just sends a bunch of fake requests to the KMS box until the threshold is reached. Then all computers in the environment happily activate without issue. KMS boxes do not communicate with Microsoft after they are setup, so you have no issues there.

If you have more than maybe 5 models of hardware, you might want to consider sysprep for the purposes of making a hardware-independent image that has all the drivers and software it needs for the models you need to deploy to. I help with over 20 models of computers, and I don’t sysprep. We used to make an image per-model in the summertime for each model we have, and we’d just deploy that image out to those models. With the driver improvements in Win10 many here on the forums are reporting they don’t have to sysprep to take a Win10 image from one model and deploy it to a totally different model PC. I myself haven’t tried it yet but people here and my co-workers have and they said it works.

Another thing to consider is deployment times. Sysprepping does slow down the image deployment time, because it’s just extra stuff that has to be done to a host before it’s ready for the user to begin using. Often times this isn’t an issue, but it is a real thing, it does slow down deployment by a minute or more depending on what you’re doing in the unattend file.

My experience is real-world experience on an enterprise level. I consider myself to have a lot of imaging experience. Now, just because I’ve done all this stuff without issue and never sysprepping, that doesn’t mean that’s what is best for you.

You might want to sysprep so you can use an unattend.xml file to do all sorts of cool post-configuration inside of FOG’s postinstallscripts area like @george1421 does where he works. You might want to sysprep just so you don’t have to worry about WSUS issues or KMS server issues, you might want to sysprep so you are sure you won’t have driver issues. You might want to sysprep simply because Microsoft recommends you do it.

@Tom-Elliott forked. @cyrmoon we are in this thread now.

This is a known issue in 1.3.2, and is fixed in 1.3.3. See the news release for details: https://news.fogproject.org/fog-1-3-3-officially-released/

I’d say just get used to the new style.

If you work at a school district, you’d actually be doing the students a disservice if you deployed this, because they wouldn’t be learning what the latest Windows OS really looks like and how to use it without all these other things that ClassicShell provides.

@Tom-Elliott Documented here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#FTP_Put.28.29:_Could_not_create_file

Probably easier to just query the DB directly using the fogstorage MySQL account. Putting together a CSV is pretty easy. I don’t know how to do it in powershell, but in BASH it’s easy to do. I can help with that, but I didn’t want to go script that until you responded saying that would work for you.

Tom’s posts are exactly correct, and George’s post is too.

I guess we should remember this in the future when explaining multi-master setups.

@Wayne-Workman said in Multicast Issues on Centos 7:

Look at this:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast

https://wiki.fogproject.org/wiki/index.php?title=Multicast

let us know how it goes, we are here to help.

Many times, I’ll post things and later on an answer is found that was already in one of the links I posted… seeing how long this thread has gone for, I’m just going to repost these links to be looked at again by the OP and any future readers.

@Jesse_K According to this article: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681386(v=vs.85).aspx

The user you’re using in FOG to join the domain, it’s password may be expired.

I have another question, I have one machine is that is on a continuous loop.

Check Task Management in the web interface to see if there is a task for this device. Tasks don’t just go away. They will stay in task management until either they are canceled or completed.

Lastly is there a way to set the fog registration screen with the options to stay a bit longer?

Web Interface -> FOG Configuration -> iPXE Boot Menu -> Menu Timeout (in seconds):*

Also, any additional questions, please ask them in a new thread.

I don’t see how exporting and importing a table or DB isn’t good enough. It does exactly the same thing in the end.

@scott-b Can you post a chunk of the c:\fog.log file showing where it adds the printer, and then where it removes it when a 2nd person logs in please?

George is right. The devs have made strides in supporting upgraded systems where all sorts of things are off/wonky due to migration not being perfect. That said, most people fail at this process because it’s perhaps beyond their skill level to fix, and when they ask for help on the forums, we have to start from zero with troubleshooting because it could be anything if it’s not obvious, and there have been a lot that haven’t been obvious fixes. I’d always recommend a clean build as George said.

Well… either your n key isn’t working, or you don’t have the right option 067 set in DHCP. Because you mistyped it many times in your post… so I assume you have misspelled it without knowing you were doing it wrong.

It’s not udionly.kpxe it’s undionly.kpxe

Check this and then come back and let us know.

@scott-b
These are interesting:

 11/29/2017 11:19 AM PrinterManager Adding printers
 11/29/2017 11:19 AM PrinterManager CutePDF Writer already exists
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Kyocera
 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox
 11/29/2017 11:19 AM PrinterManager PrintUI return code = 0
 11/29/2017 11:19 AM Printer Adding: \\printerservername\Xerox Color

Because the first one says ‘already exists’ but we don’t see the same message on the others, meaning they were not there already. This is strange. Asking @Joe-Schmitt to look at it.

@Tom-Elliott Oh, I somehow missed that. Nevermind then. -y does it all.

I understand your thoughts Quazz and although I do have another DHCP server I wouldn’t have expected it to not work so consistently if that was the case. I’d expect intermittent issues rather than it always working the first time and not the second.

Tom

Depends on your network setup. with IP Helpers - you wouldn’t notice any issues at all. If one DHCP server is set as authoritative and another is not, you wouldn’t notice any issues at all. And it too could be that the other DHCP server is just able to reply faster, consistently.

If two co-existing DHCP servers within the same broadcast domain are not properly configured to work with another present, it’ll only cause you issues.

@tywyn you realize that all windows snapins run as SYSTEM and not as administrator?