@Lee-Rowlett

physical drive
not sysprepped
2 partitions. Normal windows 10 install
MBR

i am just trying to clarify if everyone else windows 10 images launch into automatic repair or it something i am doing wrong with the way i am taking the images or my fog settings.

@irishfoguser said in resizing images windows 10:

cloned my server os drive and when i try to update using svn up and the script it fails on php7.1

never mind this.

I am now live on 1.3.5 with my main server.

I am still having the issue where windows 10 upon imaging a resizing image still reboot into automatic repair mode

cloned my server os drive and when i try to update using svn up and the script it fails on php7.1

if you ran the trunk upgrade would it not bring you to v1.4.0 RC1?

Server

• FOG Version: 1.3.0
• OS: Ubuntu

Client

• Service Version: na
• OS: na

Description

i am playing around using resizeable images instead of fixed size images but i try a test image and upload a windows 10 image. when i image it back down. When windows 10 boots up it goes into automatic repair mode and the does a startup repair and then reboots normally.

is this whats supposed to happen as that is not really something i want happening.

i know i am not running the latest fog but i am a bit anxious about the upgrade procedure on my live server as it is a very custom setup.

i have setup as a dual network setup. one card for office network and one for imaging (dhcp option). i think this setup was removed from the installer script. i also forgotten mysql root password. i also use it only as a clonging multiple systems that never connect to a domain.

Would upgrading to 1.3.5 overwrite this setup?
Do i need mysql root password to update?

thanks for the help.

@Tom-Elliott can you elaborate more.

most of my images are windows 7/8/10 and therefore are multi partition images.
so i use the option multiple partition image - single disk not resizeable.

Am i doing something wrong, I was given the admin of the server when someone left and thats what i was told what to do. the old server is 0.32 and the new one i have built myself is 1.3.0.

I want to run this script to resize images to the full size of the drive as a snapin buts its got 2 parts. Never used the snap in before.

How should i do it.

first part vbs script.

########## Extend Disk Partition (MAX) ##########
'LogFilename = "C:\Windows\Setup\InstallLog.txt"
'LogFile.writeline "-------------------------------"
'LogFile.writeline "Extending partition to max size:"
'LogFile.writeline "-------------------------------" & VbCrlf

diskpartScript = "c:\extend_max.txt"
 
Set oShell = CreateObject("Wscript.Shell")
Set oShellExec = oShell.Exec("cmd /c diskpart -s " & diskpartScript)
set oStdOutputText = oShellExec.StdOut
 
Do While Not oStdOutputText.AtEndOfStream
diskpartOutput = oStdOutputText.ReadLine
'LogFile.writeline diskpartOutput
Loop

second part is a txt file. extend_max.txt"

select disk 0
detail disk
list disk
select volume c
extend disk 0
list disk
exit

1. can i use a snpain to copy extend_max.txt and then vbs to run to an image after its imaged
2. how will it run it then?

apologies for my ignorance on snapins.

@Tom-Elliott rsync -r -n -p -o -g -v --progress --delete --ignore-existing -i -s /images/ /media/myusername/5E8D585C1892608A/images

Thanks tom. made the suggested changes and ill see what happens tonight.