I’m alone now ? …
Posts made by Jonathan Cool
-
RE: What can we do when we don't trust UUID?
To help this tread, HP Computer : ProBOOKG2 :
System Manufacturer HP System Product HP ProBook 640 G2 System Version System Serial Number xxxxxxxxxxxxxx System Type Type: Notebook BIOS Vendor HP BIOS Version N76 Ver. 01.07 BIOS Date 04/18/2017 Motherboard Manufacturer HP Motherboard Product Name 80FD Motherboard Version KBC Version 22.6E Motherboard Serial Number xxxxxxxxxxxxxxxxxx Motherboard Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz CPU Normal Speed Current Speed: 2700 MHz CPU Max Speed Max Speed: 8300 MHz Memory 7.66 GiB Hard Disk Model WDC WD5000LPLX-60ZNTT1 Hard Disk Firmware 02.01A02 Hard Disk Serial Number WD-xxxxxxxxxxx Chassis Manufacturer HP Chassis Version Chassis Serial xxxxxxxxxxxxxxx Chassis Asset ```
-
RE: Win7x64 : Golden Image : partitions problems ...
During creation process of Golden Image, in VirtualBox, i choosed Dynamic disk …
On VirutalBox, i can see : Virutal Size : 160Gb. -
RE: Win7x64 : Golden Image : partitions problems ...
@quazz said in Win7x64 : Golden Image : partitions problems ...:
Can you try leaving the file empty and see if that helps?
Failed … and same error.
But i agree with your idea and, it’s make sense.Maybe i don’t use the right process to create my VM into Virtualbox …
I choosed a 160Gb Virtual Size disk … -
RE: Win7x64 : Golden Image : partitions problems ...
I used ssh connection to copy and paste the result …
* Imaging using Partclone (gzip) Partclone fail, please check /var/log/partclone.log ! ################################################## # # # A warning has been detected! # # # #################################################### Image failed to restore and exited with exit code 1 (writeImage) Info: Partclone v0.2.89 http://partclone.org Starting to restore image (-) to device (/dev/sda2) note: Storage Location xxxxx/images/, Image name ImgUniverselle we need memory: 5247876 bytes image head 4160, bitmap 5239616, crc 4100 bytes Calculating bitmap... Please wait... get device size 159935889408 by ioctl BLKGETSIZE64, Target partition size(159936 MB) is smaller than source(171692 MB). Use option -C to disable size checking(Dangerous). Args Passed: /images/ImgUniverselle/d1p2.img* /dev/sda2 ###################################################### # # # Will continue in 1 minute # # # ##################################################### * Press [Enter] key to continue
fdisk -l on the hp2530p :
Disk /dev/ram[0 – 15] : 124 MiB, 130048000 bytes, 254000 sectors ## there is many ram disk here ... Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc91a5cff Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sda2 206848 312581631 312374784 149G 7 HPFS/NTFS/exFAT
-
RE: Win7x64 : Golden Image : partitions problems ...
@quazz Hi,
You wants a picture of the error with the HP2530 computer ?(no usb stick or any SD cards …)
-
RE: Win7x64 : Golden Image : partitions problems ...
Hi,
If i add only « :1 » in the d1.fixed_size_partitions, i have this error :
https://drive.google.com/file/d/0B48PuYLEHxQLaUMxaWpOcmRnb3M/view?usp=sharingIf i add « 2:1 » in the file d1.fixed_size_partitions and use setupcomplete.cmd to expand the space of C after deploy (by using diskpart utility, https://forums.fogproject.org/topic/1178/extend-your-disk-partition-to-max/4), it work on Optiplex7010 … but NOT in a smaller disk (hp2530p, « Target partition size is smaller than source ») …
-
RE: Win7x64 : Golden Image : partitions problems ...
Hi,
Thanks to Tom … the issue is not completely resolved but “in progress” …- I edited the d1.fixed_size_partitions : “2:1”
- after a new DL of the image, the resultt is :
https://drive.google.com/file/d/0B48PuYLEHxQLWWNDR2E0QWhPZEU/view?usp=sharing
Same result o7010, hp8000 or 640G2.
How can expand the space of C after deploy ?
-
Win7x64 : Golden Image : partitions problems ...
Server :
FOG Version: 1.4.2 SVN 6072
OS: Debian 8Client :
Service Version: SmartInstaller v0.11.12
OS: Win7x64 PRODescription :
I recently build my Win7x64PRO universal image using VirutalBox, postdownloadscripts and sysprep. It’s works perfectly but … i tried to deploy it to a small disk and partclone said « Target partition size is smaller then source » … so after some research, i discovered a big problem with my universal image : after a deploy on a big harddisk, the partitionning is not correct …
In fact, the reserved system partition is very big and the C partition is fixed like set to virtual box … How i can fix this ?
Below, i take somes screenshots to explain my problem …VirtualBox configuration :
Version : 5.0.26
VM configuration disk :
Virtual Size : 160Go
Real Size : 9,12GoWindows disk Manager on VM :
https://drive.google.com/file/d/0B48PuYLEHxQLUEU5clJOZC1Vb3c/view?usp=sharingDefinition of golden image on FOG GUI :
https://drive.google.com/open?id=0B48PuYLEHxQLdXlTcW90RS1DWncWindows disk Manager on HP8000 after deploy :
https://drive.google.com/open?id=0B48PuYLEHxQLdzRHb0EtY1k2NkUWe can see the big size of the reserved parition … not 100Mb but 72Go !
Windows disk Manager on DELL o7010 after deploy :
https://drive.google.com/open?id=0B48PuYLEHxQLSUdpam1STEV0cjgOn the optiplex 7010, same problem … the reserved partition is more larger … 305Go.
On the both computers, the system C partition is always 159Go ….
I juste want this simple partitionning :
- Reserved partition : always 100Mb
- System C partition : rest of the disk ……
I don’t use sysprep to expand or touch any partition.
What can i do to use all space for the C partition and have a classic 100Mb reserved partition ?
ls -la of universal image folder on NAS
drwxrwxrwx 2 root root 4.0K Oct 17 11:01 . drwxrwxrwx 63 fog root 4.0K Oct 17 14:20 .. -rwxrwxrwx 1 root root 3 Oct 17 10:34 d1.fixed_size_partitions -rwxrwxrwx 1 root root 1.0M Oct 17 10:34 d1.mbr -rwxrwxrwx 1 root root 190 Oct 17 10:34 d1.minimum.partitions -rwxrwxrwx 1 root root 30 Oct 17 10:34 d1.original.fstypes -rwxrwxrwx 1 root root 0 Oct 17 10:34 d1.original.swapuuids -rwxrwxrwx 1 root root 8.1M Oct 17 10:34 d1p1.img -rwxrwxrwx 1 root root 9.8G Oct 17 11:01 d1p2.img -rwxrwxrwx 1 root root 190 Oct 17 10:34 d1.partitions
cat d1.minimum.partitions
label: dos label-id: 0xc91a5cff device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 52316, type=7, bootable /dev/sda2 : start= 206848, size= 335335424, type=7
cat d1.partitions
label: dos label-id: 0xc91a5cff device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 204800, type=7, bootable /dev/sda2 : start= 206848, size= 335335424, type=7
Many thank for your help.
I worked hard to build my universal image … and now, it’s ruined by this problem
-
RE: Win7x64 : Golden Image : different profiles ...
Hi,
Thank for answers …@george1421 :
I’m not sure if i really understood your things …You said :
you may need to use persistent groups to set some default actions
Can you write an example ?You will have the most flexibility if you use the post install scripts to connect to AD
I use post install scripts to connect my AD with the desktop computer. But, for theses laptops, i don’t need to connect to AD …I think, i’m not really need to alter the unattend.xml because i use a specific unattend file for theses laptops.
You can only install “things” that windows will find during installation : yes, i understood this part
I use my specific unattend file to create my user Utilisateur. But i can’t personnalize this user with unattend …
@Seb-B : i will try your way
I will be back !
-
Win7x64 : Golden Image : different profiles ...
Server
- FOG Version: 1.4.2 SVN 6072
- OS: Debian 8
Client
- Service Version: SmartInstaller v0.11.12
- OS: Win7x64 PRO
Description
Hi everyone,
This topic is not really about an issue …
I’m searching a way to use my Golden Image to different profiles.At this point, image work with a desktop configuration by using :
- sysprep
- setupcomplete.cmd
- jonction to domain by FOG feature
- only one local user : the built-in administrator
but … for some latop in my office, we need a diffrent profile :
- no domain
- local admin
- local standard user in autologin
By the postdownload script, i can inject a specific sysprep & setupcomplete.cmd by using kernel ARGS and a simple way :
if [ $model != "VARtest" ] && [ -f "$unattendWin7" ]; then echo "Desktop computer ..." . ${postdownpath}fog.drivers . ${postdownpath}fog.ad . ${postdownpath}fog.registry . ${postdownpath}fog.antivirus . ${postdownpath}fog.bonus fi if [ $model == "VARtest" ] && [ -f "$unattendWin7" ]; then echo -n "Laptop ... Laptop is " $model . ${postdownpath}fog.drivers . ${postdownpath}fog.sysprepLaptop . ${postdownpath}fog.antivirus fi
In fog.sysprepLaptop, i copy the specific laptop unattend file into the /ntfs/Windows/Panther.
This unattend activate the built-in admin account and create a user local account by this way :
<LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>qwerty</Value> <PlainText>true</PlainText> </Password> <Description>Compte Utilisateur</Description> <DisplayName>Utilisateur</DisplayName> <Group>Users</Group> <Name>Utilisateur</Name> </LocalAccount> </LocalAccounts>
Now, i want to personnalize this standard account … for examples … :
- on desktop : some specifics icons
- in the start menu : some specifis icons
- in the taskbar : some specific icons
- ect …
- need to delete some icons into the start menu
- need to set this account in autologin …
BUT i can’t add / delete files during setupcomplete … why ? because, the user “Utilisateur” has no folder (C:\Users\Utilisateur) before her first connexion into the computer …
What is the good way to add & personnalize an account after a deploy ? … without use Sysprep / CopyProfile ?
I already use CopyProfile to set the build-in account for the desktop configuration …
Maybe 'i’m totally in a wrong way …
-
RE: Weird problem with FOG & Sysprep Win 7 x64 Pro universal image …
My bad …
After many waste of time to find the culprit, i finally found it … : me !
Why ?
Because i realized many many MANY tests (upload task, download task) to create my best-dream-universal-win7x64-image …So … i simply forgot to disable FOG service BEFORE ran sysprep on the Golden Image … (did it in the small test image)
Now, the Sysprep works fine …
But now, i know all sysprep logs … :
- cbs.log
- setup.etl
- session.xml
- setupact.log in Windows folder
- setupact.log in Windows\Panther folder
- setupact.log in Windows\Panther\unattendGC folder
- setupapt.dev in Windows\inf
- setupapt.offline in Windows\inf
- setuperr in Windows\Panther …
Shame on me !
-
Weird problem with FOG & Sysprep Win 7 x64 Pro universal image …
Server
- FOG Version: 1.4.2 - SVN Revision: 6072
- OS: Debian 8
Client
- Service Version: FOG SmartInstaller : version 0.11.12
- OS: Windows 7 PRO x64
Description
Hi all,
I’m working on my Win7x64 Golden Image and have a strange issue.
First, I would like to describe my environement and my test environement …
- All drivers, scripts and images are on a NAS
I use 2 Windows 7 PRO x64 images on a o7010 computer (same error with HP8000) :
- Small win7 image used to test scripts, drivers injection and other things … Windows updated to may 2017. No GPO.
- Golden win7 image with all softwares, all updates and all GPO for our domain.
I use SYSPREP and the same unattend file for both images.
- no antivirus program on the images
Before i capture the image (same process for the both image), i run sysprep with an fonctionnal unattend xml file.
After a deploy, i use PostdownloadScript to :
- put .cab drivers into the C:\Windows\DRV folder (with the registry hack to add this value in … the device path …)
- add some registry keys to join our samba domain (like DomainCompatibilityMode, DNSNameResolutionRequired etc …)
- copy a unattend.xml NAS file into the C:\Windows\Panther folder
- hack the unattend.xml (with sed tool) to set ComputerName, Password, MachineObject … with FOG values (domain jonction checked in the GUI)
- copy the antivirus folder on C:\ for a installation at the SetupComplete.cmd process (msi method)
In the Golden image, all reg keys has already modified before capture the image.
Not on the small Win7 image.
But, for futur, if i need to add / modify a regsitry value without rebuild image, i use fog to do that …In the Golden image, i set the GPOs.
I set no GPO on the small test image.So … if i deploy the small image on the computer, the SYSPREP works fine.
If i deploy the Golden Image on the computer, i have an error during the SYSPREP (rember, it’s the same unattend file … and same DVD installation source).
My first things : maybe it’s the unattend file …. but i tried an other test …
On my virtual machine, i open the unattend.xml and manually set the computerName … and i reboot.
The unattend works fine …
What the hell is going on ?
I saved all logs of the Golden image sysprep.
I found an error into the C:\Windows\Panther\setupact.log :2017-06-16 13:00:40, Info IBS Callback_Specialize: Internal Providers Specialized Failed. System can’t proceed to handle Internal Providers
2017-06-16 13:00:40, Info IBS Callback_Specialize: Specialize return: [1627]
2017-06-16 13:00:40, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x65bI compare the 2 images before caputre (i used the snapshot feature) for the licence count and the both said « 1 ».
If it was not a FOG issue, the SYSPREP will not work with the small image & VirtualBox image … no ?
What do you thinks about that ?
fog.postdownload :
# verifier si l image est sysprepee ou non ... unattendWin7="/ntfs/Windows/System32/sysprep/unattend_win7x64.xml"; # dirty way to determine si image universelle ou non ... if [ -f "$unattendWin7" ]; then echo "Image Universelle" . ${postdownpath}fog.drivers . ${postdownpath}fog.ad . ${postdownpath}fog.registry . ${postdownpath}fog.antivirus fi
fog.registry :
## Preparation variables & path ... cles DomainCompatibilityMode, DNSNameResolutionRequired ... ruche SYSTEM ## regfileSYSTEM="/ntfs/Windows/System32/config/SYSTEM" ## DomainCompatibilityMode ## keyLanmanWorkstationParameters="ControlSet001\services\LanmanWorkstation\Parameters" keyDomain="DomainCompatibilityMode" keyDomainValue="0x1" ........................................... ........................................... ## Edition du registre, ruche SYSTEM avec les variables definies precedemment ... ## reged -e "$regfileSYSTEM" &>/dev/null <<EOFREG cd $keyLanmanWorkstationParameters nv 4 $keyDomain ed $keyDomain $keyDomainValue nv 4 $keyDNS ed $keyDNS $keyDNSValue q y EOFREG reged -e "$regfileSYSTEM" &>/dev/null <<EOFREG ...................................................... ...................................................... EOFREG echo -e "...................................."; echo -e "...................................."; echo -e "...................................."; echo -e "\b\b\b\b\b\b\b\b\b\b\b${ceol}Registry Hack done ! Clés registres ajoutées !"; # this just removes "In Progress and replaces it with done :-)"
fog.ad :
#!/bin/sh # copie du fichier unattend depuis le NAS vers le dossier Windows ... cp -f /images/postdownloadscripts/unattend_win7x64.xml /ntfs/Windows/Panther/unattend.xml # suppresion d'un eventuel SetupComplete existant dans le dossier Windiws ... (sensible a la casse ...) rm -f /ntfs/Windows/Setup/Scripts/*etup*omplete.* # copie du fichier SetupComplete depuis le NAS vers le dossier Windows ... cp -f /images/postdownloadscripts/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/SetupComplete.cmd hostadpwd="PASSWORD"; #only downside to this method- this is the plain ad password unattend="/ntfs/Windows/Panther/unattend.xml"; if [ -f "$unattend" ]; then dots "Preparing Sysprep File"; # suppression d'un eventuel fichier unattend dans le dossier sysprep ... pour que Windows cherche uniquement le unattend.xml dans le dossier Panther rm -f /ntfs/Windows/System32/sysprep/unattend*.xml; echo "Done"; dots "Writing Computer Name"; sed -i "/ComputerName/s/*/$hostname/g" $unattend echo "Done"; dots "ComputerName Set To"; echo $hostname dots "Set PC To Join The Domain"; if [ "$addomain" != "" ]; then sed -i "/<JoinWorkgroup>/d" $unattend sed -i -e "s|<Password></Password>|<Password>${hostadpwd}</Password>|g" \ -e "s|<Username></Username>|<Username>${addomain}\\\\${aduser}</Username>|g" \ -e "s|<MachineObjectOU></MachineObjectOU>|<MachineObjectOU>${adou}</MachineObjectOU>|g" \ -e "s|<JoinDomain></JoinDomain>|<JoinDomain>${addomain}</JoinDomain>|g" $unattend echo "Done"; else echo "Skipped"; fi fi```
-
RE: unable to deploy RAID 1 disk
@george1421 said in unable to deploy RAID 1 disk:
Ok after about 5 hours of working on this I have a solution
5 hours ! It’s unbelievable !!
So, if you want some command tests output, tell us and we will help you with pleasure to debug FOGMany thank for your investigation !
-
RE: unable to deploy RAID 1 disk
Hi,
Like @george1421 said, i have a similair issue with my o3620.Can you post the results of theses commands on a debug task deployment ? :
- cat /proc/mdstat
- mdadm -D /dev/md126
For me :
- cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty] md126 : active (read-only) raid1 sda[1] sdb[0] 976759808 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sda[0](S) 5288 blocks super external:imsm unused devices: <none>
- mdadm -D /dev/md126
/dev/md126: Container : /dev/md/imsm0, member 0 Raid Level : raid1 Array Size : 976759808 (931.51 GiB 1000.20 GB) Used Dev Size : 976759940 (931.51 GiB 1000.20 GB) Raid Devices : 2 Total Devices : 2 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : d7788497:a3f2cd21:2ff72bda:c45670f9 Number Major Minor RaidDevice State 1 8 0 0 active sync /dev/sda 0 8 16 1 active sync /dev/sdb
For me, the issue is the read-only state on the array. I just want to know if you have the same issue or if it is an other issue …
Thank you.
-
RE: Windows 7 : universal image with Postdownload script : issues
Hello.
After some new researches, i found informations about sysprep.
And I discovered new issues : the unsigned drivers.
In my first attempt, I had many error during Sysprep causing by unsigned drivers. Same error on 820G3, Optiplex7010 & HP8000.
Well. I found the solution : in my reference image and before the Sysprep op, i installed two importants updates : KB2685811 & KB2685813.
After a reboot, i sysprep /generalize /oobe /shutdown the image (I took a snapshot before).
And i retry with theses computers : no error during the sysprep
And i can confirm, the SetupComplete ran : after the deploy, i can confirm :- the FOGService is started
- drivers are OK (excepted ACPI for DELL but i will fix that later)
BUT the domain jonction fail … for all computers … error 1355.
I didn’t use any unattend file … after the deploy, I answer at the questions.
There is a link about the unattend file and the FOG Domain jonction feature ? -
RE: Windows 7 : universal image with Postdownload script : issues
Oh … i’m really sorry for this mistake.
In fact, i realized some tests with Sysprep before to know the SetupComplete.cmd.
On Win10, I created an unattend file for the registry hack but … after deploy, i alway seen the OOBE screen. At this time, i said “What the hell with this screen ?” and … went back to Windows 7 for tests. Before THIS mistake, i didn’t understand the link with Sysprep and the SetupComplete.cmd but now … i think I understand
Today, i will try some tests with Sysprep.
But, just to understand, why the domain jonction feature is broken if i have a SetupComplete.cmd in the Windows\Scripts\ folder ?
You say “SetupComplete will not run” … Maybe it’s totally another problem … ? -
RE: Windows 7 : universal image with Postdownload script : issues
Hm, maybe i did a misktake.
The FOG documentation said : “f you plan to use Sysprep before image capture and are also planning to use the FOG Client” … but, i never use the “Sysprep.exe”.
On my Vbox, i just- create the SetupComplete.cmd with the script*lines
- disable FOG
- upload the image on FOG
On client, i just donwload the image …
-
RE: Windows 7 : universal image with Postdownload script : issues
@george1421 I read the OEM / VLK things.
After a “slmgr -dli”, i think i have a VLK license :
In “Description”, i can see “VOLUME_KMSCLIENT channel”.
And, the product number not start by “OEM” …Source : http://mywindowshub.com/determine-windows-license-type-oem-retail-volume/
PS : we used a KMS Server to activate all Win7 in our office.