I want all my users to not use Cached Mode

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Spin - 17 Nov 2005 01:28 GMT

Gurus,

I just re-installed Office 2003 on my Windows Server 2003 SP1. But it is
using Cached mode which is a no-no on Terminal Server. How can I make
Outlook not use Cache Mode for all new users of this system?

Signature

Spin

Reply to this Message

Jeff Pitsch - 17 Nov 2005 01:54 GMT

Was outlook installed before or after terminal services was installed? If
before, uninstall office then reinstall it.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

> Gurus,
>
> I just re-installed Office 2003 on my Windows Server 2003 SP1. But it is
> using Cached mode which is a no-no on Terminal Server. How can I make
> Outlook not use Cache Mode for all new users of this system?

Reply to this Message

Spin - 17 Nov 2005 03:41 GMT

Outlook was installed after. I used a transform file that may be settings
Outlook to Cached mode. I need to stop this behavior.

Signature

Spin

> Was outlook installed before or after terminal services was installed? If
> before, uninstall office then reinstall it.
[quoted text clipped - 8 lines]
>> using Cached mode which is a no-no on Terminal Server. How can I make
>> Outlook not use Cache Mode for all new users of this system?

Reply to this Message

Iskander - 17 Nov 2005 08:36 GMT

You could make a Group Policy for that. With Office/Outlook there's a
policy template file. Somehwere in there (the OUTLK11.ADM) there's an
option to force or disallow Cached-mode, I believe...

Reply to this Message

Jeff Pitsch - 17 Nov 2005 11:39 GMT

Heh, oops. You could use the custom maintenance wizard to modify the
behaviour as well.

Jeff Pitsch

> Outlook was installed after. I used a transform file that may be settings
> Outlook to Cached mode. I need to stop this behavior.
[quoted text clipped - 11 lines]
>>> is using Cached mode which is a no-no on Terminal Server. How can I
>>> make Outlook not use Cache Mode for all new users of this system?

Reply to this Message

Spin - 18 Nov 2005 03:15 GMT

custom maintenance wizard - do I fire that off via Add/Remove Programs?

Signature

Spin

> Heh, oops. You could use the custom maintenance wizard to modify the
> behaviour as well.
>
> Jeff Pitsch

Reply to this Message

Iskander - 18 Nov 2005 07:30 GMT

No, that's part of the Office 2003 Resource Kit.

You can find it on the following page:
http://www.microsoft.com/office/orkarchive/2003ddl.htm

Reply to this Message

Spin - 28 Nov 2005 01:49 GMT

I have downloaded and extracted source file in the link onto my system. It
generated a lot of .adm and .opa file files into a folder on the server. I
copied the .adm files into the \Windows\Inf directory. I then opened
gpedit.msc hoping to see the new policies I could do with these but I do
not. What am I doing wrong?

Signature

Spin

> No, that's part of the Office 2003 Resource Kit.
>
> You can find it on the following page:
> http://www.microsoft.com/office/orkarchive/2003ddl.htm

Reply to this Message

Iskander - 28 Nov 2005 09:06 GMT

First of all, I think it's better to make a GPO in the AD for the
terminal servers. I recommend making a seperate OU for them, if you
haven't done so already.

Make sure loopback policy processing is set in the GPO, so all you get
on the terminal server is the policies you set on the OU (set Policy
Inheritance of on the OU).

Create the new policy. Right-click on 'administrative templates' under
either the computer or user-container and select 'Add/remove
templates'. Now\ you can import the templates into the policy, and
after adding them you will see the new categories. You have to do this
for both computer and user-container.

Reply to this Message

Spin - 28 Nov 2005 13:23 GMT

Thanks. Now why do I have to do this for both the computer and
user-container. Since it's only a loopback policy only my settings in the
User portion of the policy apply correct?

Signature

Spin

> First of all, I think it's better to make a GPO in the AD for the
> terminal servers. I recommend making a seperate OU for them, if you
[quoted text clipped - 9 lines]
> after adding them you will see the new categories. You have to do this
> for both computer and user-container.

Reply to this Message

Vera Noest [MVP] - 28 Nov 2005 13:57 GMT

No, that's not correct.
Computer settings will apply + User settings from this policy (and
not from the policy which is linked to the OU which contains the user
accounts, as would happen without the loopback processing).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"Spin" <Spin@spin.com> wrote on 28 nov 2005:

> Thanks. Now why do I have to do this for both the computer and
> user-container. Since it's only a loopback policy only my
> settings in the User portion of the policy apply correct?

Reply to this Message