Best way to make Windows 10 Master and upload ?

[george1421]

Upgrade FOG to 1.4.4 to start.

Your overall process is inline with what we do at my company. But I’m pretty sure you will have better success with single disk resizable with 1.4.4. There was some bugs in 1.3.5 that kept the disks from expanding correctly. That issue was addressed in 1.4.1RC1.

[Sebastian Roth]

@laintimes This has most likely to do with your partition setup not being standard. Still you can try using the latest initrd files (64 bit and 32 bit) as we have fixed a special case just a few weeks ago.

Please post a picture of your partition setup (windows disk management) before capturing!

[laintimes]

thanks for reply
@george1421 I have updated fog to 1.4.4
@Sebastian-Roth done all the procedure described above, I am at the stage just before sysprep, this is my partition setup :

[Sebastian Roth]

@laintimes Ahh, now I guess I know what’s going wrong here. Please run the following command on your FOG server and post a picture of the output here: cat /images/WIN10X64STANDALONESYSPREP/d1.fixed_size_partitions

[george1421]

@Developers Didn’t we have an issue with the single disk resizable with FOG misidentifying the system or boot partition when the partition label wasn’t in english? Could that be the cause of the OP’s blue screen where FOG is thinking the system reserve is not fixed in size?

[laintimes]

myuserlocal@SERV-FOG:/images$ ll
total 24
drwxrwxrwx  6 fog  root 4096 jui 19 16:49 ./
drwxr-xr-x 26 root root 4096 jui 20 09:28 ../
drwxrwxrwx  3 fog  root 4096 jui 19 16:49 dev/
-rwxrwxrwx  1 fog  root    0 mar 29 11:27 .mntcheck*
drwxrwxrwx  2 fog  root 4096 mar 29 11:27 postdownloadscripts/
drwxrwxrwx  2 fog  root 4096 jui 19 15:41 WIN10X64STANDALONENOSYSPREP/
drwxrwxrwx  2 fog  root 4096 jui 19 16:49 WIN10X64STANDALONESYSPREP/

myuserlocal@SERV-FOG:/images$ cat /images/WIN10X64STANDALONESYSPREP/d1.fixed_size_partitions

cat command return empty answer

======================================================

i go another problem since upgrade fog to 1.4.4, i got loop when i try to capture :

I have check my conf :

nano /etc/exports

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

showmount -e
Export list for SERV-FOG:
/images/dev *
/images     *

sudo service rpcbind status
● rpcbind.service - RPC bind portmap service
   Loaded: loaded (/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
  Drop-In: /run/systemd/generator/rpcbind.service.d
           └─50-rpcbind-$portmap.conf
   Active: active (running) since jeu 2017-07-20 11:06:35 CEST; 25min ago
 Main PID: 1264 (rpcbind)
    Tasks: 1
   Memory: 732.0K
      CPU: 7ms
   CGroup: /system.slice/rpcbind.service
           └─1264 /sbin/rpcbind -f -w

jui 20 11:06:35 SERV-FOG systemd[1]: Starting RPC bind portmap service...
jui 20 11:06:35 SERV-FOG rpcbind[1264]: rpcbind: xdr_/run/rpcbind/rpcbind.xdr: failed
jui 20 11:06:35 SERV-FOG rpcbind[1264]: rpcbind: xdr_/run/rpcbind/portmap.xdr: failed
jui 20 11:06:35 SERV-FOG systemd[1]: Started RPC bind portmap service.

sudo service nfs-kernel-server status
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
   Active: active (exited) since jeu 2017-07-20 11:23:57 CEST; 8min ago
  Process: 3293 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 3288 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
  Process: 3283 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 3310 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
  Process: 3308 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Main PID: 3310 (code=exited, status=0/SUCCESS)

jui 20 11:23:57 SERV-FOG systemd[1]: Starting NFS server and services...
jui 20 11:23:57 SERV-FOG systemd[1]: Started NFS server and services.

/images$ ll
total 24
drwxrwxrwx  6 fog  root 4096 jui 19 16:49 ./
drwxr-xr-x 26 root root 4096 jui 20 09:28 ../
drwxrwxrwx  3 fog  root 4096 jui 19 16:49 dev/
-rwxrwxrwx  1 fog  root    0 mar 29 11:27 .mntcheck*
drwxrwxrwx  2 fog  root 4096 mar 29 11:27 postdownloadscripts/
drwxrwxrwx  2 fog  root 4096 jui 19 15:41 WIN10X64STANDALONENOSYSPREP/
drwxrwxrwx  2 fog  root 4096 jui 19 16:49 WIN10X64STANDALONESYSPREP/
myuserlocal@SERV-FOG:/images$ cd dev/
myuserlocal@SERV-FOG:/images/dev$ ll
total 12
drwxrwxrwx 3 fog root 4096 jui 19 16:49 ./
drwxrwxrwx 6 fog root 4096 jui 19 16:49 ../
-rwxrwxrwx 1 fog root    0 mar 29 11:27 .mntcheck*
drwxrwxrwx 2 fog root 4096 mar 29 11:27 postinitscripts/

ls -laR /images | grep .mntcheck
-rwxrwxrwx  1 fog  root    0 mar 29 11:27 .mntcheck
-rwxrwxrwx 1 fog root    0 mar 29 11:27 .mntcheck

I have try to restart service, reboot server, update /etc/exports, i got same issue

[george1421]

@laintimes said in Best way to make Windows 10 Master and upload ?:

Can you provide the output of this command ls -la /images/WIN10X64STANDALONESYSPREP/ Your cat command should have returned something or imaging would have failed.

The Attempting to check in error typically means that the fog server isn’t being addressed properly, like a setting is blank for the storage node IP (just guessing here).

[laintimes]

for : ls -la /images/WIN10X64STANDALONESYSPREP/

i got

[Sebastian Roth]

@laintimes Please edit the file /images/WIN10X64STANDALONESYSPREP/d1.fixed_size_partitions by hand (e.g. using nano) and put in 1. This will leave the first partition untouched on resizing.

Then deploy the image to one of your clients again and see if it boots properly.

[laintimes]

for fix : **The Attempting to check in error ** loop, after fog upgrade

FOG Configuration -> FOG Setting -> Web Server and check the FOG_WEB_ROOT path

In my case it was reset during the upgrade

@Sebastian-Roth i’m capturing standalone windows 10 install i will try your tip

[Sebastian Roth]

@laintimes Keep in mind that you need to manually edit that file every time you capture the master image again.

[laintimes]

upgrade to fog 1.4.4 seems to have solved my problem thanks everybody

nice jobs for fog project !

[Tom Elliott]

Seeing as differnt locale’s are changing the “label” of the drive to be locale specific, I don’t know of a way I can automate this.

Current checks to define “fixed size” are: System Reserved or Recovery. While I could try adding more checks, the problems come in because I don’t know what is to be labelled, how and when. I know on the english side Reserved or Recovery will be used.

[Sebastian Roth]

@Tom-Elliott said in Best way to make Windows 10 Master and upload ?:

Seeing as differnt locale’s are changing the “label” of the drive to be locale specific, I don’t know of a way I can automate this.

Current checks to define “fixed size” are: System Reserved or Recovery. While I could try adding more checks, the problems come in because I don’t know what is to be labelled, how and when. I know on the english side Reserved or Recovery will be used.

Yeah, this is an issue and I can’t see how we can fix this from our side.

[george1421]

@Tom-Elliott another FOG parameter. Not very clean but typically FOG will be installed in a unique local and not traverse across.

Possibly also something in the language file to control what the system "thinks’ the system partition is called?