Re: Precache installs question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

When you say "empty" package, do you mean the No source files in the
settings? I am new to SMS and I REALLY appreciate your response :)

"Kim Oppalfens [MVP]" <""Kim dot Oppalfen" wrote:

Jeff wrote:
Addition:

I know that installing from \\ad.domain.com\DFSnamespace will have the
client computer use the appropriate DFS replication for their subnet, but I
don't want 100+ computers hitting the DFS replication for their site at the
same time to download the install cache. I am wanting the precache to
install cacheonly from the DFS namespace, but when it comes time to actually
install the package I want it to install from their local computer cache and
not the dfs namespace. Is there a way to force this through SMS 2003?

"Jeff" wrote:

I have read all articles from
http://technet2.microsoft.com/Office/en-us/library/e3d7be86-d739-413f-8196-817899eceb771033.mspx?mfr=true

I can't find the answers I need hopefully someone can help me.

I am wanting to do the precache installs to my workstations due to major WAN
issues. Ok a few questions.

1. DFS replication of source files - do I create a namespace or just setup
replication to other locations? Reason for asking: I have to use SMS 2003
for distribution, do I make the source files for the pushed cache install to
the DFS namespace or to the actual source location and count on the
customization install locations settings (setup.exe /admin settings) for
office to "know" where to install from based on bandwidth?

2. Once the precache is installed on client computers, how do I push the
install on clients to each of their localized precache locations
(C:\MSOCache\All Users\{940120000-0012-0000-0000-0000000FF1CE}-C \setup.exe)
through SMS. I can't use GPO's for installs due to complexities of
structure, but have to use collections for phased installs.

3. If you can't use the C: drive precache, from the article how does the
pushed install know to redirect to the localized cache if you initiate
install from the network source?

Hope this makes sense, I really need help in this.

thanks


Yes, use sms distribution points instead of dfs.
Dfs is fine, and helps your clients to go to local resources, but to
achieve this you create "empty" packages inside sms, and put the full
path in the program command line. Since from "sms's" point of view the
packages are empty there is nothing to cache.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx

.

Relevant Pages

  • Re: Precache installs question
    ... I know that installing from \\ad.domain.com\DFSnamespace will have the client computer use the appropriate DFS replication for their subnet, but I don't want 100+ computers hitting the DFS replication for their site at the same time to download the install cache. ... I am wanting the precache to install cacheonly from the DFS namespace, but when it comes time to actually install the package I want it to install from their local computer cache and not the dfs namespace. ... Is there a way to force this through SMS 2003? ...
    (microsoft.public.sms.misc)
  • Re: Precache installs question
    ... DFS replication of source files - do I create a namespace or just setup replication to other locations? ... I have to use SMS 2003 for distribution, do I make the source files for the pushed cache install to the DFS namespace or to the actual source location and count on the customization install locations settings for office to "know" where to install from based on bandwidth? ...
    (microsoft.public.sms.misc)
  • Re: DFS as DPs
    ... So in essence you cannot deploy packages that contain source files to a DFS ... Do you know why legacy clients cannot reference DFS links in the SMS ...
    (microsoft.public.sms.setup)
  • RE: error 53: The network path was not found
    ... child domain names in as a DNS suffix on the SMS server. ... I am not sure of what you man by "throttling the discovery back". ... Refer to the discovery logs for more information. ... still getting these errors with no agent install. ...
    (microsoft.public.sms.setup)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I ... first time start up issues if the computer reboots after install) ... attempt at the command line from SCCM didn't. ... What if you manually uninstall Office 2003 then try running SMS ...
    (microsoft.public.sms.admin)