Prev: How not include telephone numbers and postal address when sending
Next: Category colors on shared calendars
From: TK on 18 Dec 2009 16:50
I am the IT admin of the company and to edit the registry, you need to be
the admin of the PC.

Simple question, how can I add a PST to Outlook via editing the registry...?
I have over 100 PCs and I don't want to visit everyone PC yet again.

NOTE, I use the Newsgroups to learn things I don't know. Isn't that what it
is for...?

Tom...


"Peter Foldes" <okf22(a)hotmail.com> wrote in message
news:O$Q27l5fKHA.1540(a)TK2MSFTNGP06.phx.gbl...
> Peter
>
> Yeah right . With an address as xxxxxxx @bennettcompany.com>. He is at a
> company and if that is what he wants to do then he can ask the IT person
> which would be the correct route. I think he wants to either add or remove
> email from someone's computer without anybody knowing about it. This is
> not the first time I have come across something like this
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "Peter Durkee" <pdurkee(a)mac.invalid> wrote in message
> news:eMilGx3fKHA.1540(a)TK2MSFTNGP06.phx.gbl...
>>I don't think he means the PST is password protected. He just wants to add
>>the PST to the user's Outlook without logging into the user's computer.
>>
>> -a different Peter
>>
>> "VanguardLH" <V(a)nguard.LH> wrote in message
>> news:hgdsks$2g9$1(a)news.albasani.net...
>>> TK wrote:
>>>
>>>> I believe when I insert a PST file in Outlook, it actually puts an
>>>> entry
>>>> into the registry.
>>>> Can someone tell me what this entry is so I can add the PST via editing
>>>> the
>>>> registry...? This way I don't' need the users password to add the PST.
>>>> Thanks, Tom...
>>>
>>> That password is *in* the PST file. You are not asked for the password
>>> *in*
>>> the PST file until you *open* that PST file. Even if adding it to a
>>> registry entry, Outlook will see the PST file is password protected and
>>> prompt for the password.
>>
>>
>
From: Peter Foldes on 19 Dec 2009 08:49
>I am the IT admin of the company and to edit the registry, you need to be the admin
>of the PC.

And you just proved my point

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"TK" <tkarpowski(a)bennettcompany.com> wrote in message
news:uhKoVwCgKHA.3552(a)TK2MSFTNGP06.phx.gbl...
>I am the IT admin of the company and to edit the registry, you need to be the admin
>of the PC.
>
> Simple question, how can I add a PST to Outlook via editing the registry...? I
> have over 100 PCs and I don't want to visit everyone PC yet again.
>
> NOTE, I use the Newsgroups to learn things I don't know. Isn't that what it is
> for...?
>
> Tom...
>
>
> "Peter Foldes" <okf22(a)hotmail.com> wrote in message
> news:O$Q27l5fKHA.1540(a)TK2MSFTNGP06.phx.gbl...
>> Peter
>>
>> Yeah right . With an address as xxxxxxx @bennettcompany.com>. He is at a company
>> and if that is what he wants to do then he can ask the IT person which would be
>> the correct route. I think he wants to either add or remove email from someone's
>> computer without anybody knowing about it. This is not the first time I have come
>> across something like this
>>
>> --
>> Peter
>>
>> Please Reply to Newsgroup for the benefit of others
>> Requests for assistance by email can not and will not be acknowledged.
>>
>> "Peter Durkee" <pdurkee(a)mac.invalid> wrote in message
>> news:eMilGx3fKHA.1540(a)TK2MSFTNGP06.phx.gbl...
>>>I don't think he means the PST is password protected. He just wants to add the
>>>PST to the user's Outlook without logging into the user's computer.
>>>
>>> -a different Peter
>>>
>>> "VanguardLH" <V(a)nguard.LH> wrote in message
>>> news:hgdsks$2g9$1(a)news.albasani.net...
>>>> TK wrote:
>>>>
>>>>> I believe when I insert a PST file in Outlook, it actually puts an entry
>>>>> into the registry.
>>>>> Can someone tell me what this entry is so I can add the PST via editing the
>>>>> registry...? This way I don't' need the users password to add the PST.
>>>>> Thanks, Tom...
>>>>
>>>> That password is *in* the PST file. You are not asked for the password *in*
>>>> the PST file until you *open* that PST file. Even if adding it to a
>>>> registry entry, Outlook will see the PST file is password protected and
>>>> prompt for the password.
>>>
>>>
>>

From: VanguardLH on 19 Dec 2009 13:49
TK wrote:

> I am the IT admin of the company and to edit the registry, you need to be
> the admin of the PC.
>
> Simple question, how can I add a PST to Outlook via editing the registry...?
> I have over 100 PCs and I don't want to visit everyone PC yet again.

If you think a change occurs in the registry, use a registry monitor (e.g.,
SysInternals FileMon) or host state monitor (e.g., InstallWatch) to check
what changes were made to the registry before and after using the File ->
Open menu in Outlook to load the alternate .pst file. Then you'll know
which registry entry to export (you'll probably not need all the data items
under that registry key so edit the .reg file to remove all but the
necessary data items).

One option is to put the .reg file on a networked drive access via an URN
path (\\server\share). Then use domain policies to push a login script to
the workstations that does a silent install of the .reg file ("regedit.exe
/s <urn>"). Another option is to use a policy to push a login script that
runs reg.exe to update the registry (no separate .reg file needed).

Obviously unless the user logs in under an admin-level account, neither will
work. In a domain environment, it is unlikely that all or even a major
percentage of your workstations have users logging in under admin-level
accounts (i.e., the domain puts them in an admin group that gives those
users admin permissions on their own host, not anything to do with domain
admins). However, since policies get pushed to any account (I assume) then
using policies might work to push a new login script but I'm not sure
regedit.exe or reg.exe will be usable by that pushed login script. Also,
the login script would have to be self-destructive so it doesn't get run
again; else, it just continue re-running which reapplies the same registry
change each time - and that could interfere with the user who might decide
to move their message store to somewhere else, like to a local drive that
gets backed up in an enterprise backup scheme.

I'm not and never have been a domain admin and this really isn't an issue
with Outlook which is the topic discussed in this newgroup.

> NOTE, I use the Newsgroups to learn things I don't know. Isn't that what it
> is for...?

And that retort was generated for what cause?
From: TK on 21 Dec 2009 17:25
Thank you VanruardLH

I see where you are going...

I am glad to see there are some friendly people on this news group...!

Tom...

"VanguardLH" <V(a)nguard.LH> wrote in message
news:hgj77g$t71$1(a)news.albasani.net...
> TK wrote:
>
>> I am the IT admin of the company and to edit the registry, you need to be
>> the admin of the PC.
>>
>> Simple question, how can I add a PST to Outlook via editing the
>> registry...?
>> I have over 100 PCs and I don't want to visit everyone PC yet again.
>
> If you think a change occurs in the registry, use a registry monitor
> (e.g.,
> SysInternals FileMon) or host state monitor (e.g., InstallWatch) to check
> what changes were made to the registry before and after using the File ->
> Open menu in Outlook to load the alternate .pst file. Then you'll know
> which registry entry to export (you'll probably not need all the data
> items
> under that registry key so edit the .reg file to remove all but the
> necessary data items).
>
> One option is to put the .reg file on a networked drive access via an URN
> path (\\server\share). Then use domain policies to push a login script to
> the workstations that does a silent install of the .reg file ("regedit.exe
> /s <urn>"). Another option is to use a policy to push a login script that
> runs reg.exe to update the registry (no separate .reg file needed).
>
> Obviously unless the user logs in under an admin-level account, neither
> will
> work. In a domain environment, it is unlikely that all or even a major
> percentage of your workstations have users logging in under admin-level
> accounts (i.e., the domain puts them in an admin group that gives those
> users admin permissions on their own host, not anything to do with domain
> admins). However, since policies get pushed to any account (I assume)
> then
> using policies might work to push a new login script but I'm not sure
> regedit.exe or reg.exe will be usable by that pushed login script. Also,
> the login script would have to be self-destructive so it doesn't get run
> again; else, it just continue re-running which reapplies the same registry
> change each time - and that could interfere with the user who might decide
> to move their message store to somewhere else, like to a local drive that
> gets backed up in an enterprise backup scheme.
>
> I'm not and never have been a domain admin and this really isn't an issue
> with Outlook which is the topic discussed in this newgroup.
>
>> NOTE, I use the Newsgroups to learn things I don't know. Isn't that what
>> it
>> is for...?
>
> And that retort was generated for what cause?

From: VanguardLH on 21 Dec 2009 20:38
TK wrote:

> I am glad to see there are some friendly people on this news group...!

You caught me on a good day.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: How not include telephone numbers and postal address when sending
Next: Category colors on shared calendars