Posts made by Scott Adams

Not sure how you do your imaging exactly, but you could add a section in your sysprep file that tells it to extend the partition. More specifically in the “Specialize” pass:

<ExtendOSPartition>
<Extend>true</Extend>
</ExtendOSPartition>

@dylan123 If you mentioned this already, I apologize. But, are you working with a Surface 3 or a Surface Pro 3? Everything in my environment is a Pro. I’m just wondering if we can take different hardware types out of the mix.

@dylan123 FYI, we use the 1663 adapters as well. The way I do this in my environment is I manually added a registration for each of my surface nics (I have two of them). So, when I go to image a Surface, I search for one of my mac addresses for my adapters, change the pertinent information (name, image, etc). Then, I set a deploy task to that client. From there, I can go through the steps of swapping keyboards/usb adapter (@george1421 I know I could use a powered USB hub, but I just don’t).

You could also set up a capture the same way, just choose Capture instead of deploy from the Basic tasks section.

Below are the steps that I wrote up for my environment that does work with imaging Surfaces:

1. Search FOG hosts for the Surface MAC address for the Ethernet adapter you are using.
2. Rename the host to the desired name and save changes.
3. Hold down the Volume UP button, press the power button, then release the power button. When you see the Surface logo appear center screen, release the Volume UP button.
4. In BIOS : Select Security. Under Secure Boot, change configuration, select None, click OK. Under Trusted Platform Module, change Enable TPM-Change to Off. Select Boot Config. Verify that all items are selected. Select Exit. Click Restart while holding down the Volume DOWN.
5. When the red bar shows up, release the Volume DOWN button. The device should PXE boot and go to the FOG menu.
6. Select Deploy Image.
7. Select the Surface Pro 4 image.
8. When prompted to unplug your USB NIC, unplug the NIC and plug in a USB Keyboard. Press Enter.
9. Immediately unplug the USB Keyboard and plug back in the USB NIC. YOU WILL ONLY HAVE 5 SECONDS TO ACCOMPLISH
10. Allow the device to image.
11. When the device finishes imaging, do not try to join a wireless network, just hit NEXT. Move the device to the correct OU. Run gpupdate on the device.

YRMV, but this works for us.

I don’t want to assume anything, but have you added the kernel argument for the Surface? Try and add “has_usb_nic=1” (minus the quotes).

I am able to image Surface Pro 3s and 4s, using the Microsoft Surface Ethernet adapter. Now, if only FOS could understand to look for USB nics without forcing it to search for them, that would be great.

I should also mention that since the Surface has only 1 USB port, you will need to have a USB keyboard handy. After you are able to boot to the Ethernet Adapter, it will tell you to unplug the usb nic, plug it back in, and press Enter.

Once you pull it out, plug in your USB Keyboard and hit Enter (once in FOS, the Surface keyboard will not be usable). After hitting Enter, unplug the keyboard and plug the USB adapter back in. You will have roughly 5 seconds to complete these tasks (no joke).

Hope this helps.

Was just curious. I personally enjoy class settings. The forums are a HUGE help and everyone is extremely responsive. Like I said, there is already a massive knowledge base out there on FOG.

Was just asking for curiosity sake.

I was looking through some old threads here on the forums and noticed that back in the 0.3x days, there was a class offered in Illinois. There was a cost associated with it, but you walked away with a server (desktop) fully loaded and ready to put into your environment.

I know that the forums have come SO far since then and there is a seemingly endless knowledge base, but was just wondering if the idea of another class would ever be brought up/offered again.

@danpbow I’ve used Belarc Advisor in the past. Does a great job of pulling software installed on PCs, as well as the install code (if applicable).

http://www.belarc.com/

I have attached a copy of my unattend.xml that I use with Windows 10 (edited to take out our private info). I can image Windows 10 without issues.0_1485985103092_unattend.xml

@mr626 Try the following after clearing old Windows Installations:

Remove this KEY from the Registry:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade

Remove this REG_DWORD from the Registry:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade

Set this REG_DWORD from the Registry:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\CleanupState [Set Hexadecimal Value: 7]

Run this command as Administrator:
slmgr /dli

After your operating system is activated re-run SysPrep and it should work!

The problem with Windows 10 is that the anniversary updates is not really an update. It actually reinstalls Windows on top of your current OS. So, you may not have intentionally done an upgrade, but the update actually performed an upgrade without your knowledge.

To confirm, if you look in your drive, you should see a Windows.old folder.

To get around this, you should be able to do a disk cleanup and remove previous windows installations. Once complete (and you verify the Windows.old folder is gone), you should be able to sysprep.

@george1421 I will work on getting something together and post it once complete.

In the meantime, I use Windows DHCP service (not FOG’s DHCP). I simply set my 66 and 67 scope options to my fog server and to snponly.efi ( I still have to manually change this setting as my DHCP server is 2008).

I use the actual Microsoft Surface USB Ethernet adapter. I used to have to add has_usb_nic=1, but that was not needed after a particular RC (I can’t remember which one).

Also as part of the imaging, I do have an issue with using the Type Cover. I can use it in the FOG menu, but when it wants me to disconnect the NIC, plug it back in, and hit Enter, it will not recognize any input from the Type Cover. I simple plug in a USB keyboard, hit enter, then plug my Ethernet adapter back in.

In my environment, I use both Surface Pro 3s and Surface Pro 4s.

I use snponly.efi and can image my Surfaces.

@Wayne-Workman Should this be a change I make in a separate file (maybe /opt/fog/.fogsettings? That way it will always be maintained when I upgrade.

@Wayne-Workman , that was it. Changed it to 3000 and all is well again.

Server

• FOG Version: 1.3.0 RC-23
• OS: Ubuntu 16.04

Client

• Service Version:
• OS:

Description

After updating to the latest RC, when I log into my web management, the dashboard gives me no info for my storage node.

I have verified (to the best of my ability) that all storage node passwords are correct.

Am I overlooking something simple here?

It is. No errors.

Tried, but same problem.

Server

• FOG Version: 1.3.0 RC8
• OS: Ubuntu 16.04

Client

• Service Version:
• OS:

Description

I am trying to update my server to the latest RC. I run svn up from the /root/fogproject and it states that I am on 6014. However, after running ./installfog.sh and then browsing to IP/fog/management, I am still on RC8. The update/upgrade did not happen.

Not sure what’s happening.

@MRCUR What is the group policy setting? Could be extremely beneficial to us in the education sector.

Not sure why, but the post removed my asterisks. There should be asterisks enclosing 3dbuilder and windowsalarms for the Get-appxpackage portions.