Office 2003 GPO rollout

E

Edy Werder

Dear all,


I'm testing a rollout for Office 2003 using Software Installation with
GPO for a pilot group. I made a transform with the custom installation
wizard from the ork. I selected migrate users settings


However I discovered that the normal.dot is replaced with a new one
instead of upgrading which overwrites users settings such as autotext.


I've read some posts here and it should retain the normal.dot. My
question did I something wrong by defining the transform?


Regards
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
G

Gerry Hickman

Hi Edy,

I don't know the answer, but one thing to bear in mind is whether you're
using roaming profiles.

I looked into the transforms in some detail, and my view on this, is
that you can not properly migrate, nor set user settings from transforms
in a big network environment.

The transform only seems to set the user settings on the local machine,
so as soon as a domain user logs in, the settings are lost.

As I understand it, the user settings are going to be "migrated" with
roaming profiles whether you like it or not!

The way I've set it up is as follows:

1. Don't migrate user settings (they'll be trashed by roaming profiles)
2. Don't migrate feature states (otherwise Add/Remove programs won't
reflect your choices)
3. Don't try to set any user settings in the transform - waste of time
4. Use User hive Group Policy Obect to deal with user settings

I'll have to check out if my user's normal.dot survived, I think it did
due to roaming profiles...
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
E

Edy Werder

Thanks Gerry,

I did a test with roaming profile and the normal.dot survived. However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)

I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.

Edy
 
G

Gerry Hickman

Hi Edy,
I did a test with roaming profile and the normal.dot survived.
Click to expand...

OK, that's what we expected.
However I
know of some users in my pilot group which had macros in normal.dot and they
were replaced by a new normal.dot. (local profile)
Click to expand...

OK, but these are not "roaming profile" guys?
I made some user settings in the transform and I'm not sure yet if it is
waste of time. I know GPO administrative templates is another alternative.
Click to expand...

Well I'm saying it's a waste of time in the context of roaming profiles,
as your reply seems to confirm. There's not much point altering local
profile settings on a big corporate network because as soon as someone
logs in, it's all trashed...

The Office Resource Kit docs are seriously misleading in this context,
they think everyone is running stand-alone home computers. I didn't see
anything in the ORK docs that was suitable for a big corporate network.
 

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

Similar Threads

Install Office 2003 wiht GPO 2
Default format type HTML Outlook 2013 0
Default settings for Office 2003 rollout using ORK 9
Network 2003 rollout using BITS? 1
Custom Dictionary in Office 2007 with GPO 0
Upgrading O2k3 to O2k7 via GPO 0
ose00000.exe error when upgrading from 2003 to 2007 via GPO 0
Office Upgrade via GPO and Transforms 18

Top