Office 2003 GPO rollout

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Gerry Hickman]

Hi Edy,

I did a test with roaming profile and the normal.dot survived.

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)

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.

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.

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy

 

[Edy Werder]

--
Edy Werder

Hi Edy,


OK, that's what we expected.


OK, but these are not "roaming profile" guys?

Yes they are not. Today I discovered Office 2003 renames normal.dot to
normaldot.old upon installation. Why Office do this for an upgrade I don't
know. At least the old normal.dot is still there.

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.

Okay I see your point because the GPO settings are applied before the user's
log in.

Edy