Jump to content

Recommended Posts

Posted

Hi all,

 

I have encountered a small problem when it comes to uploading my new image to the MDT server...

 

We are currently going through and building a new image for a multi-site domain which contains all of the software required for all sites (at the request of the directory of ICT!) so as you can imagine, the image is going to be huge. It is currently sitting at just under 40GB and I am about 3 quarters of the way through the build process.

 

Here comes the problem....The MDT server I am using at one of the sites isn't virtual, and it has just occurred to me that there is no where near enough space on the partition to upload to.....!

 

I have a plan, however. I am thinking of attaching an external drive to the computer, copying the entire deployment share across to the drive along with the share name, then change the deployment share path within MDT to the new partition. Theoretically, that should just work providing the share is transferred. As far as I know, the clients only rely on the share name to communicate with..?

 

Basically, I am after a second opinion. Do you think the above will work at all?

 

Any help would be greatly appreciated.

 

Thanks guys!

Posted

probably easier to just setup mdt on another server that has enough space it dosent need to be on anyhting other than a win7 box with a network connection

 

but yes as long as the ini files point at e:\deploymentshare rather than say c\d it should be fine if you share it as the same name

Posted

I have paused the image task half way through so I can make my changes to the image then auto upload. Otherwise, I would probably create another server.

 

Cool, thanks for that. I'll give it a go!

Posted

If it just looks at the share name, it should just work providing I can see that share from my reference station.

 

Only one way to find out! If it then fails, I can create a sysprep and capture task and upload it that way. At least the deployment share will be on another partition at this point.

Posted

Moving the deployment share using a Robocopy script I made seems to have done the job. All I then had to do was move the share from one folder to the other.

 

Thanks for the input!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...