Exchange server issue

[Guest]

I normally come here for development questions but this is not one and I
apologise. Couldn't find anywhere else to ask.

I recently had to install win XP on a machine for a client that had an
illegal, unactivated copy of Windows Server 2003. Unfortunately, I didn't
know the users using Outlook were dependent on the exchange server that was
setup on the "server" machine because I couldn't log into the machine to
inspect it's setup. The contracted individual who set it up originally is
being uncooperative (.

Apon logging into windows on a client machine instead of logging in via the
server, all the user settings, documents and email were prior the setup of
the 2003 server (this i expected). I backed up the entire server hardisk
before formatting and installing XP so I still have the data. The problem I
face is that I can't find my clients email post-server installation. I found
a bunch of backed up PST files which only had email prior server
installation. The next deadly move was the removal of the email account setup
in outlook to replace the exchange dependency with direct email server
settings. All the email, contacts and folders dissapeared. This was a result
of the location to delivering email to a location not being what it was
before. Lets call it "Exchange Email". I chose "Personal Folders" as I had to
chose something.

I'm used to using Outlook Express which nicley stores email in dbx databases
under each user\identity. Have I lost all the email and contacts or is it
hiding somewhere in a non-importable format?

Once again, sorry for the irrelevant post to this forum but I felt it was
fairly technical in nature. Any assistance would be appreciated (technical
articles etc). Thanks

 

[Lanwench [MVP - Exchange]]

In

I normally come here for development questions but this is not one
and I apologise. Couldn't find anywhere else to ask.

I recently had to install win XP on a machine for a client that had an
illegal, unactivated copy of Windows Server 2003. Unfortunately, I
didn't know the users using Outlook were dependent on the exchange
server that was setup on the "server" machine because I couldn't log
into the machine to inspect it's setup. The contracted individual who
set it up originally is being uncooperative (.

Apon logging into windows on a client machine instead of logging in
via the server, all the user settings, documents and email were prior
the setup of the 2003 server (this i expected). I backed up the
entire server hardisk before formatting and installing XP

Wait - you installed XP on the machine that was formerly running Win2k3 and
Exchange? Why?

so I still
have the data. The problem I face is that I can't find my clients
email post-server installation. I found a bunch of backed up PST
files which only had email prior server installation.

If they were using Exchange, the data was likely being stored in the
Exchange databases (.edb/.stm files) on the server. You can't just open it
directly.

The next deadly
move was the removal of the email account setup in outlook to replace
the exchange dependency with direct email server settings. All the
email, contacts and folders dissapeared. This was a result of the
location to delivering email to a location not being what it was
before. Lets call it "Exchange Email". I chose "Personal Folders" as
I had to chose something.

Sounds like they might've been using cached mode & OL2003, if they were able
to open their mailboxes/see their data when you'd taken the server offline.
If so, that data's probably lost, as the OST file is a mirror of the
Exchange mailbox and can't be accessed directly.

I'm used to using Outlook Express which nicley stores email in dbx
databases under each user\identity. Have I lost all the email and
contacts or is it hiding somewhere in a non-importable format?

Possible, but much depends on what was running on the server. Also, what are
their plans for a replacement server - are they buying a legal copy of
Win2k3/Exchange ?

 

[Guest]

Wait - you installed XP on the machine that was formerly running Win2k3 and
Exchange? Why?

I just started working for a Mac based company. The client was sold a
"server" machine. I believe but can't be sure of the circumstances that Win
2003 server was installed using someone elses product key. The setup of
exhange and server user profiles was done during the 30 days of usage before
mandatory activation. They were requiring that this "server" computer have
storage added to it (SATA raid using Retrospect). The machine came with an XP
license sticker on it. They run two PCs and two Macs. They don't need a
server operating system.

If they were using Exchange, the data was likely being stored in the
Exchange databases (.edb/.stm files) on the server. You can't just open it
directly.

You know when you're young and stupid, and you think you know how to switch
a system over easily and find all the problems later? Well this is one of
those days. Time to take a nasty learning curve (

Sounds like they might've been using cached mode & OL2003, if they were able
to open their mailboxes/see their data when you'd taken the server offline.
If so, that data's probably lost, as the OST file is a mirror of the
Exchange mailbox and can't be accessed directly.

The OST file still exists on the system. I was wondering what the purpose of
this extension was. Am I able to setup a mockery exchange account on another
2003 server machine and fool the Outlook cache on the client system using the
old OST file?

Possible, but much depends on what was running on the server. Also, what are
their plans for a replacement server - are they buying a legal copy of
Win2k3/Exchange ?

As I stated above, no need for a server operating system. Only one machine
was actually setup to use exchange. My bad luck was that it was the most
important machine. The existing XP license will do fine. Thanks for the swift
response. Let me know what you think. Should I be undergoing mental damage
control at the moment? P.

I will be purchasing 2003 server myself to play around with it at home. Big
investment but it'll save heartache in the future ha ha.

 

[Sue Mosher [MVP-Outlook]]

Sounds like they might've been using cached mode & OL2003, if they were able

The OST file still exists on the system. I was wondering what the purpose of
this extension was. Am I able to setup a mockery exchange account on another
2003 server machine and fool the Outlook cache on the client system using the
old OST file?

No, the .ost is connected only to the original mailbox. If the user can still log into Windows with a domain login, they should be able to start Outlook with the old profile and then export the data to a .pst file, which can be opened in Outlook without Exchange. If that's not possible, do an Internet search and you'll find a fairly expensive tool or two to hack the security on the .ost file and convert it to a .pst file.

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

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

 

[Guest]

No, the .ost is connected only to the original mailbox. If the user can still log into >Windows with a domain login, they should be able to start Outlook with the old >profile and then export the data to a .pst file, which can be opened in Outlook >without Exchange. If that's not possible, do an Internet search and you'll find a >fairly expensive tool or two to hack the security on the .ost file and convert it to >a .pst file.

Sue, with all due respect, if it was physically possible, I would have your
babies. I found myself one of those OST to PST converters. The demo got me 3
months of needed email back and the hundreds of contacts. I don't think I
could be anymore relieved. My mind was so scrambled, I didn't even think of
looking for a recovery tool. Thanks for pointing me in the right direction.
I'll work on the rest when the time comes.

I've only ever had good things to say about Microsoft and its staff. Keep up
the good work )

 

[Ken Slovak - [MVP - Outlook]]

Sue's not an MS employee. She's a volunteer providing support, as are all
MVP's. And she's married...

 

[Lanwench [MVP - Exchange]]

In

I just started working for a Mac based company. The client was sold a
"server" machine. I believe but can't be sure of the circumstances
that Win 2003 server was installed using someone elses product key.
The setup of exhange and server user profiles was done during the 30
days of usage before mandatory activation. They were requiring that
this "server" computer have storage added to it (SATA raid using
Retrospect). The machine came with an XP license sticker on it. They
run two PCs and two Macs. They don't need a server operating system.


You know when you're young and stupid, and you think you know how to
switch a system over easily and find all the problems later? Well
this is one of those days. Time to take a nasty learning curve (

The OST file still exists on the system. I was wondering what the
purpose of this extension was. Am I able to setup a mockery exchange
account on another 2003 server machine and fool the Outlook cache on
the client system using the old OST file?


As I stated above, no need for a server operating system.

My goodness, why did they buy one, then? Or, rather, why was one installed?

Only one
machine was actually setup to use exchange. My bad luck was that it
was the most important machine. The existing XP license will do fine.
Thanks for the swift response. Let me know what you think. Should I
be undergoing mental damage control at the moment? P.

I recommend a single-serving bottle of a nice crisp rosé, presuming you're
having the same heat wave we're going through here. Also, I see Sue answered
your question about theOST file. If you'd had more than one machine/user
affected by this, I'd have recommended looking at
http://www.quest.com/recovery_manager_for_exchange/ - which is something
every Exchange admin ought to have handy, in my view.

I will be purchasing 2003 server myself to play around with it at
home. Big investment but it'll save heartache in the future ha ha.

You might want to check out SBS2003. It's a lot cheaper, and is an easier
way to learn the intricacies of AD, Exchange, and whatnot.