SharedFolderScript registry in Outlook XP SP3

[Peter]

I created some forms which will be used to view email with particular "MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in shared mailbox, these emails cannot be viewed using the form corresponding to. So I add a registry key "SharedFolderScript" in " HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ". The problem solved.

However, when I use Outlook XP SP3, I add the same key in " HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ", the problem does not solve.
I would like to know whether there is some other security settings or group policy setting which will prohibit the effect of registry key "SharedFolderScript"?

Thanks.

PS. Shared Mailbox means to view another mailbox using the following procedures instead of switching to another profile: Tools -> Email accounts -> View or change existing email accounts -> Change -> More Settings -> Advanced -> Add"

 

[Sue Mosher [MVP-Outlook]]

That's the correct name for the value. Did you add it as a DWORD and set its
value to 1? Check for a possibley typo if you added it manually.

Note that the issue that the registry value affects is whether code runs on
the form. If your problem is that the UI layout is not showing, that's a
totally different matter. In that case, relevant issues are:

-- Where is the form published?
-- Does it have a read layout?

 

[Peter]

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

 

[Sue Mosher [MVP-Outlook]]

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Peter]

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

 

[Sue Mosher [MVP-Outlook]]

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Dave Schroeder]

Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.

 

[Sue Mosher [MVP-Outlook]]

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.

 

[Dave Schroeder]

Yes, as stated, I did check the user's registry hive... the value was
applied... there are no other GP items that would affect this.

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.

:

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security

:

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do
not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

That's the correct name for the value. Did you add it as a DWORD and
set
its
value to 1? Check for a possibley typo if you added it manually.


:

I created some forms which will be used to view email with particular
"MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in
shared mailbox, these emails cannot be viewed using the form
corresponding to. So I add a registry key "SharedFolderScript" in "
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ".
The
problem solved.

However, when I use Outlook XP SP3, I add the same key in "
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ",
the
problem does not solve.
I would like to know whether there is some other security settings or
group policy setting which will prohibit the effect of registry key
"SharedFolderScript"?

 

[Sue Mosher [MVP-Outlook]]

Sorry, you said you checked their registry on the server. What I was suggesting is that you check the *client* machine, both in HKEY_CURRENT_USER\Policies\Software\Microsoft\Office\10.0\Outlook\Security and in HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security, to see what had actually been applied.

Is this a terminal server environment by any chance?
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Yes, as stated, I did check the user's registry hive... the value was
applied... there are no other GP items that would affect this.

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.


:

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.

:

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security

:

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do
not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

That's the correct name for the value. Did you add it as a DWORD and
set
its
value to 1? Check for a possibley typo if you added it manually.


:

I created some forms which will be used to view email with particular
"MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in
shared mailbox, these emails cannot be viewed using the form
corresponding to. So I add a registry key "SharedFolderScript" in "
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ".
The
problem solved.

However, when I use Outlook XP SP3, I add the same key in "
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ",
the
problem does not solve.
I would like to know whether there is some other security settings or
group policy setting which will prohibit the effect of registry key
"SharedFolderScript"?

 

[Dave Schroeder]

This is in a Citrix environment... Office is not installed locally on any of
the machines in question...

Sorry, you said you checked their registry on the server. What I was suggesting is that you check the *client* machine, both in HKEY_CURRENT_USER\Policies\Software\Microsoft\Office\10.0\Outlook\Security and in HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security, to see what had actually been applied.

Is this a terminal server environment by any chance?
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Yes, as stated, I did check the user's registry hive... the value was
applied... there are no other GP items that would affect this.

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.


:

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.


:

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security

:

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do
not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

That's the correct name for the value. Did you add it as a DWORD and
set
its
value to 1? Check for a possibley typo if you added it manually.


:

I created some forms which will be used to view email with particular
"MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in
shared mailbox, these emails cannot be viewed using the form
corresponding to. So I add a registry key "SharedFolderScript" in "
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ".
The
problem solved.

However, when I use Outlook XP SP3, I add the same key in "
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ",
the
problem does not solve.
I would like to know whether there is some other security settings or
group policy setting which will prohibit the effect of registry key
"SharedFolderScript"?

 

[Dave Schroeder]

I figured out what my problem was....quite simple actually...

my .reg file contained:
"SharedFolderScript"="dword:00000001"
when it should have read:
"SharedFolderScript"=dword:00000001

..... it is now applying and functioning as it should...

This is in a Citrix environment... Office is not installed locally on any of
the machines in question...

Sorry, you said you checked their registry on the server. What I was suggesting is that you check the *client* machine, both in HKEY_CURRENT_USER\Policies\Software\Microsoft\Office\10.0\Outlook\Security and in HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security, to see what had actually been applied.

Is this a terminal server environment by any chance?
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

Yes, as stated, I did check the user's registry hive... the value was
applied... there are no other GP items that would affect this.

:

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.


:

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.


:

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security

:

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do
not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

That's the correct name for the value. Did you add it as a DWORD and
set
its
value to 1? Check for a possibley typo if you added it manually.


:

I created some forms which will be used to view email with particular
"MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in
shared mailbox, these emails cannot be viewed using the form
corresponding to. So I add a registry key "SharedFolderScript" in "
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ".
The
problem solved.

However, when I use Outlook XP SP3, I add the same key in "
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ",
the
problem does not solve.
I would like to know whether there is some other security settings or
group policy setting which will prohibit the effect of registry key
"SharedFolderScript"?

 

[Sue Mosher [MVP-Outlook]]

Good catch! That's a tough one to see.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

I figured out what my problem was....quite simple actually...

my .reg file contained:
"SharedFolderScript"="dword:00000001"
when it should have read:
"SharedFolderScript"=dword:00000001

.... it is now applying and functioning as it should...

This is in a Citrix environment... Office is not installed locally on any of
the machines in question...

Sorry, you said you checked their registry on the server. What I was suggesting is that you check the *client* machine, both in HKEY_CURRENT_USER\Policies\Software\Microsoft\Office\10.0\Outlook\Security and in HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security, to see what had actually been applied.

Is this a terminal server environment by any chance?
Yes, as stated, I did check the user's registry hive... the value was
applied... there are no other GP items that would affect this.

:

Maybe a dumb question, but did you check the registry to see if that value was actually applied by the login script? Did you also check the Policy tree to see if there was a grouip policy setting there that would override the user-preference setting that your login script sets?

Hello there, I am also experiencing the same issue, but in a Citrix
environment... the Registry Key has been applied, but it does not work. ...
to test this, I used a .reg file to be loaded when the users logged onto the
Citrix farm (loaded when logon script was run "regedit /s filename.reg)...
this is what was applied:
---------------------------------
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security]
"SharedFolderScript"="dword:00000001"
---------------------------------
I tested this with a couple of users, the entries were applied correctly (I
checked their registry hive on the server they launched Outlook from, the
entry existed). The form opened up from the shared mailbox (as it did before
applying the registry entry), but no code will execute. As a work-around the
users are able to drag the form into their primary mailbox and
complete/submit it with no issue.


:

If form code runs OK on items stored in the user's own mailbox, in public
folders, or in a .pst file, then you'll know that it's not a general
scripting issue.

To deploy the setting using GPO for Outlook 2002, you can create an
additional .adm file, using one of the existing ones to show you how they're
constructed, and add it to the GP editor.


:

I have checked the key, they have not created the key. So I created the key
manually and set it to 1. However, it does not work in their Outlook XP SP3
environment.
Is it related to Visual Basic scripting? How to set the registry key by
group policy?

If the customer is using GPO, they might already be deploying the policy
version of that key and setting it to 0 instead of 1. Check in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook\Security

:

I can use the form on Outlook 2003. However, Outlook XP SP3 shows some
problem.
Actually, in my environment, even Outlook XP SP3 can be used without
problem. But when I deploy the system to customer, their environment do
not
sound good even I put the key inside. As they have complex group policy
setting, I don't know is it related to it.
The form is published in Organizational Form folder and it has a read
layout.
Thanks.

That's the correct name for the value. Did you add it as a DWORD and
set
its
value to 1? Check for a possibley typo if you added it manually.


:

I created some forms which will be used to view email with particular
"MessageClass" defined.

In Outlook 2003, when I click the email with that "MessageClass" in
shared mailbox, these emails cannot be viewed using the form
corresponding to. So I add a registry key "SharedFolderScript" in "
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security ".
The
problem solved.

However, when I use Outlook XP SP3, I add the same key in "
HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security ",
the
problem does not solve.
I would like to know whether there is some other security settings or
group policy setting which will prohibit the effect of registry key
"SharedFolderScript"?

 

[MarshaPav]

How do I do this in a version of Outlook that isn't SP3

 

[Sue Mosher [MVP-Outlook]]

Could you tell us, please, what it is you're trying to do?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers