This would be a nice feature to have. Our hostnames are designated (Letter+Dell S/N) so that’s what the hostname must be. But if Bob says he needs a reimage, I need to go over to Bob’s PC and check the S/N or MAC. It’d be handy to be able to name a computer LR223G4 and have a searchable nickname “Bob Krabs Desktop PC”.

Posts made by THEMCV
-
Searchable nickname for hosts
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@george1421 Yeah, our names have one letter in front of the SN. Easy to get them mixed up.
Maybe it’s best to call it a day on it and just accept that I’ve got a good imaging solution limited by third party software.
Next job I’ll get it perfect.
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@george1421 What I don’t understand is why it’s so hit and miss. Right now the laptops are booting just fine without any issue, but just an hour ago I couldn’t get past it. It seems like it should be straightforward if it’ll work or not.
But I think I have a better understanding now.
And interesting. I can see how that’d pose a threat for sure. That must have been an interesting one to recover from.
Worst case scenario, we ignore PXE boot. I just love the idea of being able to automate the process entirely.
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
So what I’ve gathered and tested so far:
The issue lies in-between when FOG ends in PXE boot and when McAfee takes over.
I rebooted my computer which has never been imaged by FOG and it got stuck “Starting Operating System” with undionly.kpxe.
Switching to ipxe.pxe
allowed me to authenticate into McAfee, but Windows BSODs directly after w/PXE boot enablegoes to a black screen and does not bring up McAfeeDisabling PXE boot allowed me to boot up Windows.
Honestly, this has to be a McAfee issue or a passing issue
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@Quazz Yes, it syspreps and pulls drivers down from the FOG server.
I’ll switch that over after this test. The hunt is on.
Thanks!
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@Wayne-Workman I’m only testing right now to convert all the computers to PXE booting, so the only ones set for it first are in my office.
I’ll try changing it over to that. We disabled the encryption and so far it’s good. Sending the encryption command again and giving it a test.
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@Quazz If it’s an agnostic image, shouldn’t it not matter? It’s a VMWare image deployed, so after editing the settings and reimaging it it should still boot correctly, right?
I disabled the encryption and it’s seeming to boot fine.
Yeah, I can try that. Is that UEFI or Legacy?
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@Quazz undionly.kpxe is our default boot. We tried it again with ipxe.efi as well and in UEFI mode with no good results.
-
RE: McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
@Wayne-Workman I gave that a shot, but no dice on any of them.
I think it might have something to do with McAfee and PXE booting specifically. I switched to AHCI mode and reimaged and now it just BSODs.
1 step forward each day for the month, 100 steps back.
If we didn’t encrypt, this would be a nonissue.
-
McAfee Drive Encryption not booting into OS after PXE booting to FOG splash screen
Debian 8
FOG 1.3.0 RC-23My process: WebUI > Deploy to FOG client > FOG Client reboots into PXE > PXE Images > FOG deploys drivers > Sysprep applies unattend > Windows Boots to login > FOG Client starts from Unattend file > Client Reboots to rename > Reboots and installs all programs > User Logs In > Encryption starts > Done.
That should be it.
Here’s the problem. After the user (me in the situation) logs in, reboots, and gets past the FOG menu and goes to the McAfee Drive Encryption login, it won’t boot. It does its
Resetting Hardware... Disabling Mouse... Disabling Mouse... Starting Operating System...
Then it hangs, but only if it PXE boots into FOG before hand.
I have no clue where the error lies because clearly FOG has already passed the torch to McAfee, but if I disable PXE booting it works just fine.
Such a weird issue and I’m hoping somebody has had it before.
I can answer any questions that you may have for me.
Thank you
-
RE: Backing up user profiles/data before deploying image
@george1421 I will take a look at that, thank you!
Yeah, I feel where you’re coming from. Which is why I’d like folder redirection so we don’t have to worry about them too much, but many of our users are mobile and I’ve heard some syncing horror stories.
-
RE: Backing up user profiles/data before deploying image
@Tom-Elliott Huh, yeah I suppose I didn’t think about that with the infections. I would hope that McAfee would grab it, but who are we kidding. It’s McAfee.
We have some users who are having issues (first time FOG deployment here for a user) and that’s just something that’s come up. I’m trying to make it so I can tell it to image and the process is done from there. No touching it or anything. Just image and you have a new PC in 20 minutes.
-
RE: Backing up user profiles/data before deploying image
@george1421 How do you guys use USMT? See, I wondered about pulling their profile up before the FOG client rebooted them, then it pushed it back down similar to how the script works, but I don’t know that Windows will just accept the profile that’s there or if it’ll make a new one. Our computers are single user PCs.
-
Backing up user profiles/data before deploying image
Debian 8
FOG 1.3.0 RC-23I ran across this thread as I’m trying to find a solution for this
Backup Feature for user profiles/Data
FOG has changed in 4 years so I wasn’t sure if this scripts was something that could ever be implemented or if there was a better solution. Folder redirection, offline mode, and roaming profiles aren’t out of the question yet, but if we can use FOG I’d rather.
The main issue right now is that our drives are encrypted with McAfee and so in order for this to work I suppose the FOG client would have to do the heavy lifting.
If this isn’t something that can be done in general or for my environment, I’m okay to be told it can’t.
Thanks!
-
RE: Home button on FOG WebUI has the e in Home underneath of Home
@Tom-Elliott Okay.
I figured I’d at least put it in the bug report channels to have it officially noted
-
Home button on FOG WebUI has the e in Home underneath of Home
Server
- FOG Version: 1.3.0 RC-23
- OS: Debian 8 jessie
Description
Home button on FOG WebUI has the e in Home underneath of Home. This is only fixed by zooming out all the way and back in, but returns when the page refreshes. I’ve notice this for a while, but wanted to document that the issue exists.
Minor bug, but still a bug I suppose.
Chrome Version 54.0.2840.99 m
-
RE: Unable to multicast; FOGMulticastManager fails to start
@ryanxplosion Honestly, try Debian 8 out and install FOG on it. Ubuntu I’ve had to tweak a lot and had multiple issues getting it to work right. Debian is good out of the box.
I would just try that and see if it works.