thanks, i figure up what’s the problem, i’ve add corrupted lines on /etc/fstab.
thanks for everything.
everything is working now.
🙂

@Bob-Henderson You might enjoy Snappy Driver Installer, although this is generally more useful if you get all sorts of models accross the floor, rather than expected ones as it will have drivers for close to everything. (compressed)

@oraniko you need to keep in mind the client runs as Windows service, which gets run as SYSTEM (that is, a non-interactive user). This means you’ll need to take non-supported approach to get this working. Change
net use r: \ph.ph.biu.ac.il\Programs MYPASSWORD /user:DOMAIN\MYUSERNAME
to
net use r: \ph.ph.biu.ac.il\Programs MYPASSWORD /user:DOMAIN\MYUSERNAME /persistent:yes

Now, you need to keep in mind SYSTEM now owns this network mapping, and so only SYSTEM can remove it. In addition, Microsoft doesn’t really support this, so its likely the drive will show as disconnected for all users, but it should still be accessible if they try to open it.

Perhaps a better approach would be to make a GPO logon script to auto mount these network shares.

thanks dude 🙂

@oraniko sweet. See just a little knowledge (where to look) grants great power.

@oraniko can you update to 1.3.5 and see if the problem is still present?

@oraniko When a snapin or snapinpack runs forever, usually this means it’s waiting for input. And snapins are not allowed to receive input, nor interact with the end-user in any way.

So, to troubleshoot, Step back and start without even involving fog. Unzip all these files to somewhere - open an elevated command prompt, cd to the directory and run setup.exe and see what happens. If it doesn’t “just go” without asking for any input whatsoever - then it needs work. Once you have it “just going” without any help, take that work and those commands and make a snapin or snapinpack with them. The links I posted below are full of resources & ideas.

@george1421
Thanks a alot 🙂
that works now

@oraniko Either you want us to help you fix the issue or you want to do your own thing.

FOG RC 15 and 16 where both released 15 actually hopefully having a fix to the problem you’re describing.

If you really want to go back to 1.3.3 that’s up to you, but doesn’t help us fix what the problem actually is.

@oraniko yes you found that pxelinux.0 is not wanted/needed with the current version of fog.

Thanks a lot for the fast response
that worked perfect!