Perhaps I should expand. This is what I did up to v1607. My sysprep answer file sets autologon of Administrator for 99 times. It enables the Administrator account and has the password included (hashed by sysprep). It also includes a FirstLogonCommands to run a cleanup script. That cleanup script performs the first part to remove security, rewrites the RunOnce registry value, then restarts the computer. Because the RunOnce registry value was recreated, the auto logon of Administrator launches that script again to perform further functions. After 3 more restarts the script turns off autologon, does not rewrite the RunOnce, re-enables security, then shuts the system down. With v1709 I changed how I harvest driver files and have been able to install all drivers without the need to dumb down the security. I now install all general drivers from setupcomplete.cmd .

@aksl Are keen to get your hands dirty and dive into “compiling and debugging iPXE”?? If yes is your answer, there is a way I could lead you.

You’re very welcome.

THANK YOU GILOU!!!

FOG and Windows 8/8.1 can work with the UEFI default of 4 partitions (Partition 1 usually being the Protective MBR, Partition 2 being the Recovery, Partition 3 being whatever it is microsoft decided it to be, and Partition 4 being the main data partition) This is what is typical of a default Windows 8/8.1 install with UEFI enabled. Yes, the file system is also structured in GPT which also should work fine. Under the Default Windows 8/8.1 setup, with UEFI enabled, the only requirement before an imaging task occurs is to disable Secure boot, and re-enable it once the imaging task is complete. Maybe you could try the latest and greatest in SVN to see if it may help you with the default partitioning scheme done by the Lenovo installation disks? I’ve try to make as dynamic as possible and rely purely on the disk layout scheme over specifically telling the HDD where and what partitions to place.

@Dee DM me with specifics and I’ll see if I can help.

Hello, I’ve upgraded to SVN 2906 and this problem is resolved. I now see a sensible page if I call up the login history. Thanks Alasdair

@george1421 Wouldn’t Know How To check if it’s in the repo, but I can give it a shot almost home.

@SeqSupportEdkey please see @brianjones2007 's request. Brian, you might want to head over to iPXE and look for a guy named Micheal Brown… Or you could further elaborate your problem here and we will do our best to assist. It may be something that we know the solution to… sometimes it works that way.

@Sebastian-Roth @Tom-Elliott After an update to the current subverion it’s working again. Thanks.

Just wanted to update. I have been busy here at work so I have not been able to do anymore testing on the init files. So sorry for the delay.

@Towndrunk said in Multicast won't start: Is there any benefit to updating all the time if there is also the potential to have things not work? The benefit - getting a bug you report fixed. Getting bug fixes others report. Updating is totally up to you. Nobody is forcing your hand, and Release candidates are just that. Release candidates. If you want to sit on it, you can. If you want to update, you can. However - if you have issues and ask for help here, and the devs/mods/testers know your issue is fixed in a later RC, we will ask you to update and won’t offer much help with getting your older RC to work, when all you would need to do is update. Of course we’d help with the updating itself if you had problems. But it’s all still up to you.

@Wayne-Workman said in New Fog client and security: @LibraryMark said in New Fog client and security: It’s just that for my situation, in a public library with public hosts on a network totally separate from our staff net, I am not sure I have a need for bullet-proof security there. You’re public users are not a security risk? And I know you say you have HDD locking software (Centurion SmartShield or Faronics DeepFreeze probably), but this doesn’t really matter. If there’s a security hole and someone knows how to exploit it, they can exploit it every time they want. Once there’s a compromise, those computers are no longer safe for users to use, no matter how many times they are rebooted and ‘reset’. The legacy client is not secure. The legacy-enabling functionality server-side is also not secure. It is advised that once you have moved to the new fog client, to remove legacy passwords from the FOG server. We are using Reboot Restore Rx. Are you talking about the fog client still?

@george1421 I’m 99% sure it was the suggestion of something I found on the forums a long time ago, but simply forgot. Like I said, once everything calms down, I’m planning on rebuilding my FOG machine anyways, and blast away old images, especially since I can drop driver packs in now :)

@maxcarpone Unfortunately our build server seems to play up. Has not started building yet and I am not sure why…

[quote=“mpmackenna, post: 893, member: 373”] [LEFT][COLOR=#333333]I have the below error over and over again in my FOG log viewer. I checked to see if my /var/www/fog/commons/config.php file had the correct settings and it does. I also was able to log in to the mysql db on the fog box without trouble. The db is on the same local machine as the FOG installation. Can someone please tell me how I can further troubleshoot this error?[/COLOR][/LEFT] [LEFT][COLOR=#333333]I am running FOG 0.32 on Debian 5.[/COLOR][/LEFT] [LEFT][COLOR=#333333]Thanks,[/COLOR][/LEFT] [LEFT][COLOR=#333333]Mike[/COLOR][/LEFT] [LEFT][COLOR=#333333][01-30-12 1:12:13 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT] [LEFT][COLOR=#333333][01-30-12 1:12:23 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT] [/quote] My problems with task hanging and getting [COLOR=#333333]“Failed to connect to database server” messages, [/COLOR]were solved by changing “WOL_INTERFACE”, “eth0” from 0 to “eth1” in both config files /var/www/fog/commons/config.php and /opt/fog/service/etc/config.php

@Vickie-Osbornr said: Asus X200M Are we working with this one?

@dcorpening You would probably be best off upgrading to FOG Trunk. It would also be helpful if you could post a short video of the boot process so we can see it, or a series of pictures of the last thing the computer is saying before exiting to the local Windows.

Here is the file I used. 0_1486506949560_SetupComplete.cmd Place your SetupComplete.cmd in %windir%\Setup\Scripts (you will nedd to create the scripts folder.) Copy your unattend.xml to %windir%\system32\sysprep\ hit windows key and S, type service, click on services, find FOG and right click and select propereties, select disable click apply. hit the Windows key and R to open the run box, type in sysprep. double click the sysprep icon. Hope it works for you.

@unknownhost99 i just want to let everybody now that the server functions properly know thanks to everyone who replied, it was a great help and i love the service you supply keep going at it!