@xfirero Please check https://forums.fogproject.org/topic/7765/pxe-booting-into-ms-windows-7-setup

@Kiweegie No, you ran this command

./bin/installfog.sh

which indicates you are not in the bin directory.

@Tom-Elliott https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile

@Wayne-Workman It seems like this is not necessary on Pro versions of Windows, but it is on Home Premium! At least that’s how my test situations have turned out so far. In Home Premium it seems to copy over literally everything and in Pro it is more clever about it.

Just unselect the WOL option?

@arnaudrigole He’s saying that if you have less than 30 computers to image simultaneously you could use the normal way of deployment with Quick image for example in the mean time.

Could you tell us what OS FOG is running on? And which revision you’re at? (number in the cloud on the WebGUI)

@Wayne-Workman Theoretically it will use the current shell to try and execute it, yes.

But unexpected newline is typical of a wrong interpretator in my experience.

@Wayne-Workman Due to the difficulty in removing this file under Windows (close to impossible), this should be deleted after the profile is copied to the NAS, so that when you deploy it it gets deployed without the incorrect metro registry settings.

@Satheesh You don’t have to uncheck WOL if it’s not enabled on the machine. Try instant deployment instead, should work.

Images are always uploaded to the Master node of the group.

@JJ-Fullmer Perhaps try the /IT (interactive) switch

@Quazz Scratch that, it still seems to cause issues, but I’m looking into some ntuser.dat stuff to fix it.

@Satheesh There are numerous things that could cause delayed deployment to not work, one of them being your server timezone being incorrect somewhere. There’s a FOG setting for timezone you could check and of course on your system itself.

@x23piracy There is no space between your item return and the <— which there should be!

It’s currently item return<—

It should be item return <—

I should have caught that way earlier, lol.

An option to block mobile user agents seems easiest to implement.

@Quazz Well that didn’t solve anything, so I’m going to try out a little program called Defprof which should supposedly be compatible with W10 and do everything I hope it does.

@Satheesh What version are you on? I ran a quick test and delayed deployment works fine for me.

As soon as the designated time hits, I boot it up and it starts to do its assigned task.

@Lestat86 After you click on that, can you go to the Apache error logs and post the lines of when you clicked on Advanced?

@latelier What FOG version are you on? I’m thinking you’re on 1.2

XFS support was only added in Trunk I believe.

Defprof was able to do everything I hoped, everything is working exactly as it should.

One of the key parts I noticed is they have their own program which you have to install to handle the Windows Apps.

Also default wallpapers need to be placed in the Users/Public

There’s a ntuser.dat hiding there as well which might have an impact on default profiles.

For now though, I have a way to handle Windows 10 perfectly.

Additionally, from what I gather from Defprof is that it’s a bad idea to remove the Default folder becuase of the junction points contained in it.