Workstations Ask For Office CD

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If MS Office was installed from an Office Admin Point on a server then it
stored the server name as part of the value and the MS Installer is
basically expecting to find a connection to its installation source for
feature repair etc. This article may be helpful to you.
http://support.microsoft.com/kb/297168/
=======
We recently installed a new Windows 2003 Server network. The old network
server ran Windows Server 2000 which was disconnected from the new network.

After the new network took over, user workstations and shared workstations
started asking for the MS Office CD. I believe this was for ver 2000 and/or
XP. Office 2003 is fine. My predecessor plugged the old Windows Server
2000
back into the network and that ended the requests for the Office CD.

I want the old server off the network. Can anyone advise me how to resolve
the issue of user computers wanting the Office CD? But, they look for the
old server for this information.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[Steve]

My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If the server named change you can use the script/registry change in the
prior article to add a location that the MS Installer (used by Office 2000
and newer) uses to locate a 'home' (source) install location. It's used for
autorepairing, roaming users and features that may not be used 'until used'
by a particular machine or user.

You can also use the procedure here, but it's involving each workstation
and a recache.
http://support.microsoft.com/kb/267362/en-us?fr=1

For additional information you may want to look at the Microsoft Office
Resource Kit for your version of Office at
http://microsoft.com/office/ork/2000

=======
My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which
server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If the server named change you can use the script/registry change in the
prior article to add a location that the MS Installer (used by Office 2000
and newer) uses to locate a 'home' (source) install location. It's used for
autorepairing, roaming users and features that may not be used 'until used'
by a particular machine or user.

You can also use the procedure here, but it's involving each workstation
and a recache.
http://support.microsoft.com/kb/267362/en-us?fr=1

For additional information you may want to look at the Microsoft Office
Resource Kit for your version of Office at
http://microsoft.com/office/ork/2000

=======
My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which
server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.

 

[- Bob Buckland ?:-\) -]

Hi Steve,

If the server named change you can use the script/registry change in the
prior article to add a location that the MS Installer (used by Office 2000
and newer) uses to locate a 'home' (source) install location. It's used for
autorepairing, roaming users and features that may not be used 'until used'
by a particular machine or user.

You can also use the procedure here, but it's involving each workstation
and a recache.
http://support.microsoft.com/kb/267362/en-us?fr=1

For additional information you may want to look at the Microsoft Office
Resource Kit for your version of Office at
http://microsoft.com/office/ork/2000

=======
My predecesor is the one that did the previous installations. The knowledge
of what was done left with him. I don't know if they were installed
seperately. I saw today that they are Office 2000. The user computers do
look for the old server (there was only one) that is no longer online (a new
2003 server network with 5 servers was just installed as I was hired). I
believe that office 2000 was installed on that old server, and that is what
the user computers are looking for.

Everything you guys said is right on.

Am I correct that I can install office 2000 in a folder on one of the new
servers and then get the user computers to look for it there the issue is
solved? The article seems to solve the problem, but I do not have the
ability to write the necessary code to change the source list or which
server
to do it on. Is there any other way to point the users computers to a new
folder with office 2000 in it?

I very much appreciate your patience with me. I'm learning.