@george1421 I am building my reference image on a VM and then the unattend.xml in Windows System Image Manager.
Posts made by mlnancejr8808
-
RE: Certain Dell models are not enjoying my Universal image
-
RE: Certain Dell models are not enjoying my Universal image
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ExtendOSPartition> <Extend>true</Extend> </ExtendOSPartition> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>*</ComputerName> <CopyProfile>true</CopyProfile> <ShowWindowsLive>false</ShowWindowsLive> <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey> <TimeZone>Eastern Standard Time</TimeZone> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <AdministratorPassword> <Value>SomeEncodedPassword</Value> <PlainText>false</PlainText> </AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>SomeEncodedPassword</Value> <PlainText>false</PlainText> </Password> <Description>LocalAdministrator</Description> <DisplayName>Administrator</DisplayName> <Group>Administrators</Group> <Name>Administrator</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipRearm>1</SkipRearm> </component> </settings> <cpi:offlineImage cpi:source="wim://fs1/data/software%20distribution/microsoft/windows%207/sw_dvd5_win_pro_7w_sp1_64bit_english_-2_mlf_x17-59279/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
-
RE: Certain Dell models are not enjoying my Universal image
It doesn’t look the unattend.xml worked at all for this model. The local admin account was disabled, the drive didn’t extend, and it won’t add to AD automatically. Any ideas? I definitely need this one figured out because we have skids of OP755s going out for student use.
-
RE: Certain Dell models are not enjoying my Universal image
These are the steps I followed to build my unattend.xml is there anything I can or need to change to fix this? The second option in what you sent worked, by the way.
Open the Windows System Image Manager (the WAIK executable for our next step)
In the Bottom Left frame right click Select a Windows image or catalog file.
Browse to the extracted Windows 7 folder \Sources\install.wim and click Open.
Now we need to configure these unattended installation configuration. The settings are similar for an x86 installation but I’m going to be focusing on the 64 bit configuration in this guide.
Under Windows Image expand the section Components.
i. Scroll down to amd64_Microsoft-Windows-Security-SPP_ (NOT the UX!!)- Right Click -> Add to Pass 3 Generalize
- You’ll now see it appear under Components -> Pass 3 Generalize in the Answer File Frame.
- Select it, and in the right frame Microsoft-Windows-Security-SPP set SKIPREARM to 0
ii. On the left frame scroll down to amd64_Microsoft-Windows-Deployment_neutral - Right Click -> Add to Pass 4 Specialize
a. Expand amd64_Microsoft-Windows-Deployment_neutral
b. Right Click -> Extend OS Partition -> Add to Pass 4 Specialize
c. Select in the middle frame
d. In the right frame set
i. Extend -> True
e. Back in the left frame Expand -> RunSychronous
f. Right Click -> RunSynchronousCommand -> Add to Pass 4 Specialize
g. Select in the middle frame, and in the right
i. Action -> AddListItem
ii. Order -> 1
iii. Path -> net user administrator /active:yes
iv. Windows 7 natively disables the local admin account, we want to make sure it’s turned back on.
iii. On the left frame scroll down to amd64_Microsoft-Windows-Shell-Setup_Neutral - Right Click -> Add to Pass 4 Specialize
a. Select and add the following settings to the right frame
b. ComputerName -> *
c. CopyProfile -> True
d. ProductKey -> If you use a KMS server you can enter the generic KMS client key for your copy of windows. Otherwise enter your Volume Activation License key.
e. ShowWindowsLive -> False
10
f. TimeZone -> your current time zone. NOTE the documentation isn’t clear on how to enter these. You need to fully write it out e.g. Eastern Standard Time
iv. In the left frame scroll down to amd64_Microsoft-Windows-International-Core_neutral - Right Click -> Add to Pass 7 oobeSystem
- Select in the middle frame
- In the right frame.
a. InputLocale -> en-US
b. SystemLocale -> en-US
c. UILanguage -> en-US
d. UserLocale -> en-US
v. In the left frame scroll down to amd64_Microsoft-Windows-Shell-Setup_Neutral - Right Click -> Add to Pass 7 oobeSystem
a. DisableAutoDaylightTimeSet -> False
b. DoNotCleanTaskBar -> True - Expand amd64_Microsoft-Windows-Shell-Setup_Neutral
a. Right Click -> OOBE -> Add to Pass 7 oobeSystem
i. HideEULAPage -> True
ii. NetworkLocation -> Work
iii. ProtectYourPC -> 1
b. Expand -> UserAccounts
i. Right Click -> AdministratorPassword -> Add to Pass 7 oobeSystem - Set Value – to your desired local administrator account password.
ii. Right Click -> Local Accounts -> Add to Pass 7 oobeSystem
iii. Right Click -> Local Accounts in middle frame
iv. Insert New Local Account - Action -> AddListItem
- Description -> LocalAdministrator
- DisplayName -> Administrator
- Group -> Administrators
- Name -> Administrator
v. Set password to match previous administrator password.
vi. 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
-
RE: Certain Dell models are not enjoying my Universal image
Its Win7Pro x64. Partition layout is just a standard Windows, nothing fancy, 40GB size. Built off of a VM. Sysprepped with a unattend.xml
-
Certain Dell models are not enjoying my Universal image
I have created a universal image for all of our PC models in our school district. I had successful testing on 6 models, both Dell and HP then I hit a snag. I have been unable to successfully image on Dell Optiplex 755s, 380s, and 390s. It will go through the imaging process without an issue, start the Windows setup to install the drivers get to 100% on the driver install and then say that it cannot complete setup. Has anyone had this issue? I have used driverpacks for my drivers but I have also pulled the driver files from working PCs out of C:\Windows\System32\DriverStore\FileRepository. Any help would be greatly appreciate because of course, I have a overabundance of 755s and that has to be one of them that isn’t working.
-
RE: Blinking cursor after imaging Windows 7 32-bit on a Dell Optiplex GX250
Tom,
I loaded it as MPS. It works great now! Thank you for all your help! -
RE: Blinking cursor after imaging Windows 7 32-bit on a Dell Optiplex GX250
single disk, ntfs only, resizeable
-
RE: Blinking cursor after imaging Windows 7 32-bit on a Dell Optiplex GX250
I received as follows:
[root@10/]# gdisk -1 /dev/sda
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not presentFound invalid GPT and valid MBR: converting MBR to GPT format.
Disk /dev/sda: 312500000 sectors, 149.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E9E53B7B-C649-426D-AAB3-B22F4843D866
Partition table holds up to 128 entires
First usable sector is 34, last usbale sector is 312499966
Partitions will be aligned on 2048-sector boundaries
Total free space is 3127005 sectors (1.5 GiB)Number Start (sector) End (sector) Size Code Name
1 2048 309374975 147.5 GiB 0700 Microsoft basic data
[root@10 /]# -
Blinking cursor after imaging Windows 7 32-bit on a Dell Optiplex GX250
Hello all,
I have uploaded the image successfully, it seemed to image on the client PC successfully but when it tries to boot to the HDD it sticks on a black screen with a white blinking cursor…any ideas/thoughts? -
RE: Imaging stuck on upload after finished
I am on version 1.1.2. Did the upgrade from 1.1.1 to 1.1.2 this morning.
-
RE: Imaging stuck on upload after finished
I have deleted the old image file that I am replacing this with. The file is never being created for the new one.
-
RE: Imaging stuck on upload after finished
Also when it goes to the upload screen its says its cloning /dev/sda1/ to /tmp/pigz1 is this correct?
-
RE: Imaging stuck on upload after finished
I have deleted the image file, tried recreating it and it has not shown up in /images. I’m guessing the permissions aren’t working correctly or something isn’t matching. Here is what it looks like when I run ls -l /images
drwxrwxrwx 2 fog root 4096 Jun 23 13:02 360WIN7
drwxrwxrwx 2 fog root 4096 Jun 25 08:42 520STUDENTWIN7
drwxrwxrwx 2 fog root 4096 Jun 13 10:35 6300STUDENT
drwxrwxrwx 2 fog root 4096 Jun 13 12:15 6300TEACH
drwxrwxrwx 2 fog root 4096 May 19 14:29 740TEACHWIN7
drwxrwxrwx 2 fog root 4096 May 16 13:33 745STUDENTWIN7
drwxrwxrwx 2 fog root 4096 May 16 13:32 755TEACHWIN7
drwxrwxrwx 2 fog root 4096 May 16 13:16 760TEACHWIN7
drwxrwxrwx 2 fog root 4096 May 19 13:58 760WIN7HS
-rwxrwxrwx 1 fog root 8980811625 Feb 10 14:56 acer_2011
drwxrwxrwx 2 fog root 4096 Mar 3 11:55 D531WIN7
drwxrwxrwx 7 fog root 4096 Jun 24 09:07 dev
drwxrwxrwx 2 fog root 4096 Mar 12 11:34 E6410WIN7
drwxrwxrwx 2 fog root 4096 May 19 13:30 HP6200Student
drwxrwxrwx 2 fog root 4096 May 19 14:51 HP6200Teacher
drwxrwxrwx 2 fog root 4096 May 16 10:43 HPNETWIN7
drwxrwxrwx 2 fog root 4096 Jan 27 10:39 HPProDesk600
drwxrwxrwx 2 fog root 4096 Mar 27 09:09 LENOVO
drwxrwxrwx 2 fog root 16384 Jun 29 2010 lost+found
drwxrwxrwx 2 fog root 4096 Jun 29 2010 _olddev
drwxrwxrwx 2 fog root 4096 May 21 13:00 WYHS740WIN7
drwxrwxrwx 2 fog root 4096 May 19 14:00 WYHS755WIN7 -
RE: Imaging stuck on upload after finished
I have changed the permissions on all of this and it is still not working.
-
RE: Imaging stuck on upload after finished
I am having this issue. I am having some issues getting the permissions to change correctly. Can anyone give me some pointers on this? all of my filles have root as an owner instead of fog.
-
RE: Database update failed 1.1.0 to 1.1.1
I know this may be a stupid question, how did that happen and can i get it to where i can run 1.1.1? Will 1880 run/act differently?
-
RE: Database update failed 1.1.0 to 1.1.1
I did the upgrade to 1.1.1 and it still saying that I am not on the latest version. Also, on the main login page for the WebGUI, instead of the cloud in the upper left hand corner saying FOG 1.1.1 it says FOG 1880. then under \var\www\fog\commons I don’t have a config.php file anymore.
-
RE: Hostname CHanger not working since moving to 1.0.1
I may be doing this wrong but does the image need to be in workgroup instead of being on the domain when uploaded for a imaged client to add to the domain?