Skip to main content

moving configmgr package shares to an alternate location

ever since sms got into the business of managing security updates, it’s been a struggle trying to make sure that distribution points are sized right for the amount of content they’re going to be hosting.  we’re all clowns in a circus and should be quite adept at juggling by now.  :)

once you’re beyond that small hurdle, you may find yourself in the same pickle when you start venturing into OSD.  even in a san world where drive space can magically show up on your server, it’s still often easier to get additional drive space than it is to increase existing drive space.

i had to do a bit of reshuffling recently and found this blog post from the manageability team blog immensely helpful:  http://blogs.technet.com/smsandmom/archive/2008/09/04/moving-the-smspkgc-share-to-a-different-drive.aspx.

there is one caveat though that my coworker enlightened me about.  if you’re using bits-enabled distribution points (and i imagine the majority of us are), you’ll want to make one additional change.  any distribution points utilizing bits will have a corresponding virtual directory which will need to be adjusted to the new location.  to do this, fire up your internet information services (iis) manager.

  1. navigate to site server\web sites\default web site\sms_dp_smspkg[x]$.
  2. right-click the virtual directory and choose properties.
  3. in the local path field, change the path to the new location.

[x above is the drive letter.]

 

here’s a screen shot of what to do. image

 

comments always welcome.  hope you get some good mileage out of this.

Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »