Posts made by agray

@Sebastian-Roth

@george1421 said in Connecting FOG to Virtual Machine:

the network adapter as bridged or NAT?

Bridged

@george1421 said in Connecting FOG to Virtual Machine:

What device on your network is providing dhcp info?

A router that is on a closed network. It is only connected to the Machine that is running fog and 3 outputs for machines i hook up to it, nothing else.

I can’t seem to get my VM to communicate properly with my FOG server.
I’m using Oracle VM Virtualbox 6.0.
I have my VM successfully booting into iPXE but won’t get the options from the fog server.
Any suggestions on how to fix this?

@george1421 said in Windows Sysprep Breaking:

If you only make 1 or 2 images a month you can use MDT directly and not use FOG to clone your systems.

We image, on advantage around 10 an entire year. we are just looking for a quick fix if something brakes and we need one out fast.
Even though MDT bootable, like you said, isn’t fast; it seem simpler than this long process with FOG, at least for my needs.

@george1421 So MDT is basically adding more steps to take out the time of windows updates?
MDT would make basically be my physical machine would be easier to restart every time it fails?
I have yet to try and capture a VM using FOG so I may have some issues with that, I don’t think the process would be much different, right?

@chris178 Can you explain you set up to me a bit.

Is your machine set to DHCP?
If so you might need to boot into it and do an ip and dns flush.

@george1421 I looked into MDT and it looks a lot easier and simplifies FOG. There is a problems I am seeing and would like to know how you work around them.

1. How does Fog interact with the WIM files?

@Taspharel I don’t have access to the logs. The sysprep goes through properly until I boot it back up; then it provides an error and will not boot at all.

@george1421 My Windows 10 UBS is from the media creation tool but inside my unattend.xml, it has our volume license product key. Do I need to use the iso from the volume license?

Sorry I’ve been on medical leave so I haven’t had time to work on this, but, unfortunately, it is not solved.
I have made my own unattend.xml file, i am following this guide (https://forums.fogproject.org/topic/9877/windows-10-pro-oem-sysprep-imaging/11) almost exact. Using it’s batch file and operations but not using a setupcomplete.cmd
I personally think it’s something i’m doing in the audit mode. I’m not connecting to our Domain but I am setting a static IP for just installation process, then change it back to dynamic for sysprep and capture.
The software I am attempting to install is the following: VNC, Java, .Net, Silverlight, VLC, Firefox, Chrome, Cute pdf, Munis, Laserfiche, Office 365 (not activated), Sophos Endpoint, Comm Portal

@george1421 Should i register before sysprep or during the sysprep boot? Or does it even matter?

@george1421 How do i capture without register with FOG?

@george1421

When you say register, do you mean activate? If that is the case, I typically don’t activate it while building the golden image. You really have 3 days to play with the image before it starts to complain about activation. We activate it post image deploy in the setupcomplete.cmd batch file.

fog, the first time it sees a machine, it asks you to register the machine, either full or quick.

This is one way to do it. Its not a problem. The only issue is when you deploy your image, you can’t/shouldn’t boot the system into windows while its connected to the imaging network if the target computer needs to connect to AD. In your setup you will when you create the deploy task, tell FOG to power off the target computer after image deployment. That way you can move the target computer to the business network before its powered on.

Not sure, if for what ever reason, I’m imaging different and it’s working. we boot UEFI>tell fog to quick register it>Select capture (on fog machine)>boot into “onboard NIC” and it captures or deploys the image we select on the fog machine

I guess I’m confused and having the issue with order of operations.

My set up is:
FOG is on it’s own network with not net access. Completely off our network since our network is 100% static.

How we capture images:
Setup PC on our network -> Set to DHCP and hook up to switch connected to FOG and capture
Deploy it the same only reversed.

Does this pose a problem with creating a Golden img?

@Tom-Elliott I’m sorry, what service are you referring to?
@george1421 I will attempt to set this up in a VM on my FOG machine and then update this thread.
Should I register the device before i sysprep or after? This could have been part of my problem as well.
Rules of thumb are: Don’t connect to AD and don’t use OEM. right?
Would the Media creation tool work or do I need to burn our volume license iso to a usb?

Answering the questions don’t take long. Is there a tutorial on how to properly set up an unattened.xml file and using it properly?
Was a physical machine but I’ll probably try VM on my fog server.
I don’t use command line, I went to the file location and just used the application.

I feel I’m doing this 80% wrong.

I’m not using an unattened.xml file because I don’t quite understand it and, from what I have read, it’s not required for a golden image.
It was an OEM installation of window.

Could the problem be the OEM/AD?

In several attempts to create a windows 10 golden Image, I keep receiving the error “Windows could not finish configuring the system. To attempt to resume configuration, restart the computer.” I then restart the computer and it gives me the same error.

In prep for the image, I enter Audit mode, as explained here:(https://forums.fogproject.org/topic/9877/windows-10-pro-oem-sysprep-imaging).
In my order of operations, I enter audit mode, join our domain, install required software, leave domain, sysprep.