@sebastian-roth No problem i can create separate images for same sized disk but first milestone is to make sure it is possible. I will give it a try and share here.
Latest posts made by abuadal
-
RE: Deploying Image without Data Loss
-
RE: Deploying Image without Data Loss
@sebastian-roth said in Deploying Image without Data Loss:
@abuadal said in Deploying Image without Data Loss:
I tired that but it didn’t worked.
Please provide more details on why it did not work. Maybe it’s just a minor thing we can tweak to get this to work but need more information! Provide a picture of the error on screen when you deploy with a missing
d1p5.img
file in the images directory.I captured an image from a computer with 500GB HDD and deployed on a 1TB HDD with some raw/ dummy data on D Drive. It rewrite the partition table and removed the D drive. However it did worked for the C drive (OS drive).
Now my next workaround is to find the way out to deploy the OS without loosing partition table or without loosing data on D drive. -
RE: Deploying Image without Data Loss
@sebastian-roth said in Deploying Image without Data Loss:
While it sounds interesting I am not sure this will work in this scenario. Though it’s worth a try. The partition layout cannot be stripped as FOS will always wipe and deploy the partition layout as a whole. The only chance I see is remove d1p5.img file and try a deployment.
I tired that but it didn’t worked. It simple increased the size of OS drive (C Drive) and consumed the whole space.
I believe there must be some way out to deal with this scenario. -
RE: Deploying Image without Data Loss
@Tom-Elliott Thanks for the response.
My OS drive (C drive) is 100GB in all computers so you can say that it is same for all computers. However the size of Data drive (D Drive) may vary depending on the size of disk. In some computers it is 500GB and in other it is 1TB. -
RE: Deploying Image without Data Loss
@george1421 said in Deploying Image without Data Loss:
If you want to exclude just that 5th partition from deploying to other computers, I think maybe the easiest solution is to capture your source computer with single disk resizable (yes that will capture that 5th partition too), then we can go into the raw data files and remove any reference to that 5th partition. So you will initially capture it but then remove it from the FOG server so all deployments will only have 4 partitions.
Thank you @george1421 for your guidance and quick response.
Actually the 5th drive is data drive which definitely contain different data for each computer.
So I intend to clone and deploy only the core OS related drives that are common in all scenarios.
Can you please guide me further about the 2nd part of your reply as i am quite new to FOG and this forum and i have absolutely no idea how to do this. I came to know about FOG last week and since then I am doing experiments to achieve my goal and I am just able to deploy on a blank hard disk. Your help will really help me achieve my goal.
I want it in a way that if OS of any of my computer got corrupt, I don’t have to format or disturb my D drive (Data Drive) and just get my OS and programs deployed within shortest time. In this way I can get my computer ready within shortest possible time without disturbing the existing data n my computer.
Once again thank you so much… -
Deploying Image without Data Loss
Hello Everyone,
I have windows 10 Pro with C and D drive but technically it have following;
I just want to clone the partitions in the red rectangle and don’t want my data drive (partition 5) to be cloned.
I want to use this image for all the deployments with different sizes of disks but same number of partitions.
Can anyone of you please guide me.
Thanks in advance.