upgraded Office 2003 reboot lose user profile

[keith]

I upgraded a multi-user computer from Office XP to 2003.

Now after every reboot all users lose there settings - ie outlook asks users
to set up acounts.

Very frustrating. Suggestions?

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

I should add that this was dome via a network disk image, and that we are in
a workgroup, not domain.

Reading the other posts based on the search term "Profile", it looks like
this is a common problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312596 suggests that
I need to copy the disk image to the local machine to install, then all the
registry entries will be made correctly and the problem solved.

Has anyone had success with this? We've a site licence and always installed
office via network, but this looks like that is no longer a feasable method.
Comments?

Keith

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved

 

[keith]

Solution:

Give the user administrative privilidges.
Open and run office to set up accounts, printers, etc.

Can't say why any user should run with less than admin priviliges if that's
the case - shouldn't you get a warning at least here?

Peeved