Re: DST and update

On Feb 28, 10:55 pm, "cptkirkh" <k...@xxxxxxxx> wrote:
On Feb 28, 10:52 pm, "cptkirkh" <k...@xxxxxxxx> wrote:





On Feb 28, 7:06 pm, "Gregg Hill" <b...@xxxxxxxxxxx> wrote:

Bharat,

Yes, mine had an explicit deny, but my wife's Domain Power Users account did
not, which is why I created a temporary new user called ExchangeDST to use
for the updates (detailed in four paragraph of my post).

There is (used to be?) a way to make Domain Admins have full access, but I
could not find it, so I just created the new user.

Gregg Hill

"Bharat Suneja [MVP]" <bharatsun...@xxxxxxxxxxx> wrote in messagenews:eTbGdA3WHHA.4180@xxxxxxxxxxxxxxxxxxxxxxx

If your account (which is a Domain Admin) also has Exchange Full Admin,
Exchange Full Admins have explicit Deny on Full Mailbox Access.

The docs talk about that, and it's recommended to create another account
with Exchange View Only Admin permissions and member of Local Admins on
the box you're running the tool on, then run the script to provide
explicit Full Mailbox Access and Send As perms on mailboxes that need
updating.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------

"Gregg Hill" <b...@xxxxxxxxxxx> wrote in message
news:eSR1o72WHHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
The only way I got it to work is to do the following (History first, fix
second).

History: In the ESM on the server, since I am a domain admin, I added my
wife's account to have full access to all mailboxes. I made her a local
admin on my workstation, then I logged into my workstation using my
wife's account, logged into Outlook, closed Outlook, and then ran the
configuration tool (version 2) under her account to create the batch
file, then ran the C:\Program Files\MsExTmz\sbs2003\MSExTmz_1.bat batch
file.

That failed to work.

So, on my server (SBS 2003 SP1), I created a new user called ExchangeDST
and gave that user full permissions to all mailboxes, just as I had with
my wife's account. I then made that user a local admin on my workstation,
then I logged into my workstation using that account, logged into
Outlook, closed Outlook, and then ran the configuration tool (version 2)
under the ExchangeDST account to create the batch file, then ran the
C:\Program Files\MsExTmz\sbs2003\MSExTmz_1.bat batch file. These are the
same steps I did with my wife's account.

It worked perfectly. I have no clue why the same steps using my wife's
account failed to work. My wife is a member of the Power Users group, but
other than that, I am lost as to why it now worked.

To summarize:

1) On your server, create a new user called ExchangeDST and give that
user full permissions to all mailboxes using the ESM
2) Make that user a local admin on a workstation, then log into the
workstation using that account
3) Using the same account, log into Outlook, close Outlook
4) Run the configuration tool (version 2) under the ExchangeDST account
to create the batch file
5) Run the C:\Program Files\MsExTmz\sbs2003\MSExTmz_1.bat batch file.
6) Delete the ExchangeDST user from the ESM permissions and from AD

That worked for me.

Gregg Hill

"cptkirkh" <k...@xxxxxxxx> wrote in message
news:1172686343.406894.327510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I went through all of the aricles and now i am going through the steps
on KB930879 and I ran the grant full admin script. I then run the
MSEXTMXcfg file and setup my batch files and the folder with my email
servers name. I then run the batch file found inside on jsut acouple
of users and I keep getting the logon box for the email client and
error message 0x8004011D. What could I be missing? Thanks for your
help.- Hide quoted text -

- Show quoted text -

How do you give Exchange view only permissions and full mail box
access in the ESM?- Hide quoted text -

- Show quoted text -

Bharat,
My user did have a mapi profile. I am going to try creating a
brand new account like Greg did but I a confused on how you can give
Exchange view and full admin access in the ESM. If you could
enlighten me on that I think that may get it to work for me. You know
the funny thing is that it worked on some of my mailboxes but not all
of them.- Hide quoted text -

- Show quoted text -

Gregg,
Your suggestion worked thanks for your help.

.

Relevant Pages

  • Re: DST and update
    ... Yes, mine had an explicit deny, but my wife's Domain Power Users account did ... which is why I created a temporary new user called ExchangeDST to use ... In the ESM on the server, since I am a domain admin, I added my ... under the ExchangeDST account to create the batch file, ...
    (microsoft.public.exchange.admin)
  • Re: DST and update
    ... Yes, mine had an explicit deny, but my wife's Domain Power Users account did ... which is why I created a temporary new user called ExchangeDST to use ... with Exchange View Only Admin permissions and member of Local Admins on ... under the ExchangeDST account to create the batch file, ...
    (microsoft.public.exchange.admin)
  • Re: Running a script from an ASP page
    ... the account does not have to be admin. ... >> accessible to the NT User token using ASPEXEC (depends on authentication ... >>>I have a batch file that moves files from one server to another, ...
    (microsoft.public.inetserver.iis.security)
  • Re: wierd batch file behavior
    ... I ran the batch file in a cmd window and watched it carefully. ... net localgroup Administrators /add Admin /domain ... backspace),and finally make that account an administrator. ...
    (microsoft.public.scripting.wsh)
  • Re: wierd batch file behavior
    ... I ran the batch file in a cmd window and watched it carefully. ... net localgroup Administrators /add Admin /domain ... backspace),and finally make that account an administrator. ...
    (microsoft.public.scripting.wsh)
Quantcast