Deploying Office XP with SMS

J

jro

Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

jro said:
Hello, I'm deploying Office XP using a MST file with SMS
(I would prefer to use SMS over Group Policy). I have no
problem deploying Office XP. In the MST file I provide and
alternate server incase the primary distribution share is
offline.

The problem I'm having is when you first launch Office XP
it want to find the resource files from the original
distribution share (which is on the SMS Server). Since SMS
creates a distribution package that is not shared and even
if you share the package Office XP looks for the source
files with a UNC path so it fails and will not go to the
alternate server I provided in the MST file (since the
original server is still online).

Is there a way to solve this issue with SMS? If I deploy
Office XP this way everyone will get a dialog box looking
for the source files. Thanks for any help!!

We solved the problem by creating a Package server in addition to the
SMS server. We store the SMS packages as well as the distribution files
on that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 
C

Courtney

Courtney said:
We solved the problem by creating a Package server in addition to the SMS
server. We store the SMS packages as well as the distribution files on
that server.

When the SMS package executes, it gets the distro directly from the same
server.

This worked for over 3,0001 so far.... :)

courtney sends....

That's 3,001. not 30,000.

courtney sends...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top