-
@jackiejack yes, first thing you do is go into audit mode… do the windows updates in the virtualbox before sysprep (be sure to select bridged network adaptor) so you’ll be able to upload to fog. Put network drivers for all models in c:\windows\inf folder somewhere. You could install software before sysprep if you want. The only software we install before sysprep is Microsoft Office and do the rest post image.
-
@larosejm no I mean in my current real machine. Can I go into audit mode, then install the rest of my programs? Is that how it works?
-
@jackiejack you could use a physical machine, but virtualbox is easier and transerable… your machine doesn’t matter. I actually use virtualbox on a mac… from some notes… “install Windows using Audit Mode* in virtual box with 4gb ram, 2 processors, 50gb dynamic hard drive, bridged adapter”
-
@larosejm NO
I have a machine with some installed programs. I have more programs to install in it. Can I go into audit mode now and install the rest of the programs? Or do I have to start over (in a VM this time)? -
@jackiejack definitely start from scratch. Its quick enough, and if this is your image your gonna use on a bunch of machines, you want it to be perfect… plus it’ll be easier to document all the steps you do.
-
@larosejm Right. Hopefully I could get another machine somewhere…
-
@jackiejack Somebody should draw a flow chart or something. Ahhhhhh
-
@jackiejack you don’t need another machine… install virtualbox on your current machine… you can export it when you get everything good to a network share somewhere
-
So can I follow these steps exactly for my win 10?
-
@jackiejack You can, but they are mostly wrong for your current setup.
-
When I change network adapter from NAT to bridged in virtualbox, I loose network connectivity in both host and guest. My host says network cable unplugged. When I power off virtual machine, host reconnects fine. Power on virtual machine, no internet connectivity on either guest or host.
… or should I post this on a virtualbox forum?
-
@jackiejack said in Win 10 image:
or should I post this on a virtualbox forum?
You better do so. Unfortunately I don’t think we are able to properly help you with that. Though there might be people around having had this issue too. Not sure. But you’re definitely better off posting this virtualbox-specific problem in their forums.
-
@george1421 said in Win 10 image:
@jackiejack You can, but they are mostly wrong for your current setup.
No what I mean is for the SIM part. Can I follow it? Or this one:
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/settings-for-automating-oobe
Or this one
http://searchenterprisedesktop.techtarget.com/tip/Create-a-hands-free-Windows-10-install-image-for-the-OOBESee what particular scares me is section 25 v 2 b vi of https://forums.fogproject.org/assets/uploads/files/1469134024622-fog-universal-image-setup-win-7.pdf?v=78s341l4bha
she says
It seems odd to add this twice, but otherwise after sysprep it will still
prompt for an initial local account name. It may be possible to remove
the OOBE section, but I haven’t experimented with it.Since I wanted a fully automated install of win 10 (with 2 admin accounts) should I follow this windows 7 guide? Or use the other links?
Or create the local admin accounts in audit mode first (not in SIM) then SkipUserOOBE but they say that is deprecated.
