It appears that when the Outlook 2007 client does a "send/receive", it also synchronizes the Exchange Mail box with the OST-Offline Folders.
We have one user that has a 2GB *.ost. She connects to the chair's mailbox, of which contains about 5GB of data. Hence, at 2GB *.ost.
She is having trouble synching calender entries she created to his calendar. I believe it is because the size is so large, the ost file is corrupting.
There is no way to natively view the ost (it is not a pst), unless you use some third party application.
The fun for today....
Friday, March 26, 2010
Tuesday, March 16, 2010
SMS 2003 Schema - older version of sms schema extensions
For some reason, automatic site discovery is not working in our sms environment. I also noticed that "older version of the sms schema extensions" is being logged in the sitecomp.log.
1) I need to setup a SLP (Server Locator Point) in SMS Admin. Actually, I had already done it, but it still was not working.
2) I needed to extend the AD schema with SMS schema extensions. I thought I had done this, but it appears that I haven't. Actually, because I have installed SP3, apparently, I need to run the schema extender app for SP3, as new classes\attributes are created.
Unpack SP3 for SMS 2003 and check out:
\SMS2003SP2\smssetup\bin\i386 for extadsch.exe
1) I need to setup a SLP (Server Locator Point) in SMS Admin. Actually, I had already done it, but it still was not working.
2) I needed to extend the AD schema with SMS schema extensions. I thought I had done this, but it appears that I haven't. Actually, because I have installed SP3, apparently, I need to run the schema extender app for SP3, as new classes\attributes are created.
Unpack SP3 for SMS 2003 and check out:
\SMS2003SP2\smssetup\bin\i386 for extadsch.exe
Friday, March 12, 2010
Exchange 2003 Server crash...
On Monday, our Exchange 2003 server had a hard crash, which caused corruption of our (4)four datastores. Needless to say, I have not had this much trouble with Exchange in a while. After much research, I basically did the following:
1. Renamed the datastore directories and deleted the corrupted datastores after backing them up to another drive (took 4 hours to backup over 1MB link – upgraded it to 1GB while the system was down). Went into the Exchange Admin console and created new blank datastores.
2. Restored the four datastores from Friday’s (March 5th) online backup – (after 1GB link set, it took only 2hrs for 125GB of datastores).
3. Ran: Eseutil /r E00 /l “y:\mdbdata\Exchangelogs” /s “y:\mdbdata\Exchangelogs”
4. Ran: “eseutil /g” on each datastore
5. Ran: “eseutil /p” to each to repair each datastores, (took about 1 hour each), which allowed me to finally mount them.
When I ran the “eseutil” commands above, the E00.log was the one that was created when I generated new databases to do the restore, not the one on the system had when it crashed. However, I have the transaction logs from Friday 5th-8th that I think I want to replay, if it won’t cause harm, because some users are missing emails from the period between Friday Mar 5th and when the system crashed on Monday evening.
My Question is (two-part):
A. Do you know if one can replay older transaction logs using “eseutil” on a currently running Exchange server?
B. If I can, do you know if I can replay the logs while the server is online, or do I have to stop the datastores, then run the command?
1. Renamed the datastore directories and deleted the corrupted datastores after backing them up to another drive (took 4 hours to backup over 1MB link – upgraded it to 1GB while the system was down). Went into the Exchange Admin console and created new blank datastores.
2. Restored the four datastores from Friday’s (March 5th) online backup – (after 1GB link set, it took only 2hrs for 125GB of datastores).
3. Ran: Eseutil /r E00 /l “y:\mdbdata\Exchangelogs” /s “y:\mdbdata\Exchangelogs”
4. Ran: “eseutil /g” on each datastore
5. Ran: “eseutil /p” to each to repair each datastores, (took about 1 hour each), which allowed me to finally mount them.
When I ran the “eseutil” commands above, the E00.log was the one that was created when I generated new databases to do the restore, not the one on the system had when it crashed. However, I have the transaction logs from Friday 5th-8th that I think I want to replay, if it won’t cause harm, because some users are missing emails from the period between Friday Mar 5th and when the system crashed on Monday evening.
My Question is (two-part):
A. Do you know if one can replay older transaction logs using “eseutil” on a currently running Exchange server?
B. If I can, do you know if I can replay the logs while the server is online, or do I have to stop the datastores, then run the command?
Creating a custom WinPE for WIM install
We use static ips here and since SMS OSD Install Image CD will only use dhcp, I've decided to create a custom WinPE that will format the primary drive, set a static IP, and connect to our SMS server and apply our standard pc image "wim" file. Modified the Startnet.cmd, created a diskpart script file, and used the windows AIK for the winpe image.
The technet article: http://technet.microsoft.com/en-us/library/cc709665(WS.10).aspx has been my guide.
I'll let you know how it goes.....
The technet article: http://technet.microsoft.com/en-us/library/cc709665(WS.10).aspx has been my guide.
I'll let you know how it goes.....
Thursday, March 11, 2010
Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable
I had to changed my private 1GB iSCSI network port on my SMS 2003 box, to the front side. Tried to use terminal services to get to the box and received "Unable to obtain Terminal Server User Configuration. The RPC server is unavailable".
Also, I noticed that I could not map a drive to the box.
After looking at some posts, I realized that I had not enabled "File and Print Services" and "Client for Microsoft Networks". Enabled these, and things were working again.
These settings had been disabled originally because I did not need them for iSCSI traffic talking to our storage.
Also, I noticed that I could not map a drive to the box.
After looking at some posts, I realized that I had not enabled "File and Print Services" and "Client for Microsoft Networks". Enabled these, and things were working again.
These settings had been disabled originally because I did not need them for iSCSI traffic talking to our storage.
Subscribe to:
Posts (Atom)
