RemoteInstall Folder – C to D Drive

Hi,

I wish to change my RemoteInstall folder from my C drive to my D drive, as you can imagine it is filling up. Does anyone have any experience in this and how exactly is it done. Is it just a case of creating a new distribution point on the D drive and use this instead? Would this be a viable option?

Any help greatly appreciated

Declan D

February 25th, 2009 11:05am

Hi,

If I understand you right then you're talking about to move your Distribution Point to another drivecause your default smspkgc$ share is filling up your C drive.
Here are two options:
  1. You could create new site system --> server share and use a dedicated share on your prefered drive on that server. Afterwards you could distribute your new (and even your old)packages to that share.
  2. You could move your smspkgx$ share to another drive. A How-To can be found here: http://blogs.technet.com/smsandmom/archive/2008/09/04/moving-the-smspkgc-share-to-a-different-drive.aspx
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2009 8:31am

Hi,

If I understand you right then you're talking about to move your Distribution Point to another drivecause your default smspkgc$ share is filling up your C drive.
Here are two options:
  1. You could create new site system --> server share and use a dedicated share on your prefered drive on that server. Afterwards you could distribute your new (and even your old)packages to that share.
  2. You could move your smspkgx$ share to another drive. A How-To can be found here: http://blogs.technet.com/smsandmom/archive/2008/09/04/moving-the-smspkgc-share-to-a-different-drive.aspx
February 26th, 2009 8:31am

Remoteinstall belongs to WDS server, so the procedure for moving DP related stuff don't apply here ...
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2009 8:38am

This is making no sense.

Whenever I create a PXE Service Point in my Configuration Manager I see that a new folder called SMSPXEIMAGES$ under a folder RemoteInstall. Whenever I update any of my boot images I see that they are sent to this folder. This is the folder that I choose when updating my distribution points for example.

So which folder should I be using?

February 26th, 2009 2:03pm

Hi Declan,

I just had this once andtested it in a VM. My SCCM server has a C and D drive. My C drive was larger then my D drive so by default SCCM uses the C drive to store packages.

Perhaps you used to store everyhing on the D drive but when this is filling up SCCM will use the second largest hard drive.

Did you configured WDS manually? I installed WDS did not configure it since this must be done by the PXE Service Point. When adding the PXE role the Remoteinstall folder is also created on the C drive.

I removed everything and now placed a plain textfile at the C drive with the filename no_sms_on_drive.sms (where .sms is the file extension). Now when you repeat the installation steps everything is placed at the D drive. By creating the file you tell SCCM not to use that drive so it will look for the second largest drive. This also counts for the SMSPKGx$ (where x represents your drive letter) share.

It is normal behavior that the SMSIMAGES folder on the RemoteInstall folder is shared as SMSPXEIMAGES$ and that this folder is used to store the uploaded boot images.

Hope this explains it in more detail.

- Jannes Alink

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2009 9:43am

Hi,

Agree with all in this thread :-) It is the WDS remote installation folder you would like to move to D:\remoteinstall - check this step by step guide -http://windowsitpro.com/article/articleid/13908/how-do-i-move-the-distribution-point-for-remote-installation-services.htmlor simply remove the the WDS service/PSP role, reinstallWDS to d:\ and add the PSP role again.

February 27th, 2009 10:00am

Ok, I think I know where I have made my faults and what the explanation is and I will do my best here to explain it. If I am wrong in any of this, someone please step in and let me know.

I am using Configuration Manager for Operating System Deployment this means that even though Windows Deployment Services is installed, I am not using it. I am using the services it supplies but that is it.

So, originally when I enabled the PXE folder I saw nothing in my C drive, however when I went to copy the boot images to a distribution point (which is usually your first action if you are using OSD) I saw that there were two DPs. I choose the second one that had the share name of SMSPXEIMAGES$ (orginal folder name is RemoteInstall which now I have realised that even though I am not using WDS, this is the DP for WDS! I need to choose the first DP I see in the list which is the DP for SCCM, this is called SMSPKGD$

This clears up the confusion why I/everyone will have two DPs

To move my DP then to my C drive to my D drive, was very simple in the end. I took the following steps:

1 Remove the Boot image files from the DP

2 Remove the PXE Service point server role from my configuration manager server.

3 Deleted the following folders from my C drive:

RemoteInstall / SMSPKGD$ / SMSSIG$

4 Rebooted my server

5 Created a simple text file called no_sms_on_drive.sms

6 Enabled the PXE Service point server role on my configuration manager server

7 Noticed that the following folders were NOT on my D drive

RemoteInstall / SMSPKGD$ / SMSSIG$

8 Regardless I went ahead for the boot image files (when copying them to a DP specified to create a new DP and specified the first DP on the list and NOT the SMSPXEIMAGES$ folder! Once I had done this (afterwards) the following folders had appeared on my D drive but I noticed that the did not have the share icon

9 - Rebooted the server and now the three folders had the share icon

This is how I did it

Whew!

Is this clear for everyone what happened?

I put the no_sms_on_drive.sms file on my C drive so no SMS componet would be created there. When I created the PXE service point no folders were created on the D drive, the only happened when I selected that something be copied to the DP.

Strange but true!

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2009 10:19am

hey man, do this:

stop wds service:
wdsutil /Uninitialize-Server

copy c:\RemoteInstall folder to new drive

then:
wdsutil /Initialize-Server /REMINST:"D:\RemoteInstall"

start wds service or restart server.

done.

  • Proposed as answer by MR. LONSKi 4 hours 57 minutes ago
April 5th, 2015 10:39pm

hey man, do this:

stop wds service:
wdsutil /Uninitialize-Server

copy c:\RemoteInstall folder to new drive

then:
wdsutil /Initialize-Server /REMINST:"D:\RemoteInstall"

start wds service or restart server.

done.

  • Proposed as answer by MR. LONSKi Monday, April 06, 2015 2:38 AM
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2015 2:38am

hey man, do this:

stop wds service:
wdsutil /Uninitialize-Server

copy c:\RemoteInstall folder to new drive

then:
wdsutil /Initialize-Server /REMINST:"D:\RemoteInstall"

start wds service or restart server.

done.

  • Proposed as answer by MR. LONSKi Monday, April 06, 2015 2:38 AM
April 6th, 2015 2:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics