Exchange PowerShell Commands :-
Exchange PowerShell Commands
Posted by viralr on March 28, 2012
Posted in Exchange Server 2010 Posts | 2 Comments »
Exchange 2010 EMC “initialization failed” error execution of scripts is disabled on this system
Posted by viralr on November 15, 2011
Exchange server 2010 and I have just launched the EMC and received the following error.
Initialization failed
ConsoleInitialize.ps1 cannot be loaded because the execution of scripts is disabled on this system
Cause :-
—————
The reason for this error is the security setting on your pc that does not allow you to execute a script. This is the so-called Execution Policy. By default, the Execution Policy is set to Restricted. This setting means that you may not run any PS1 script at all.
An overview of the policy levels:
Restricted: Individual cmdlets can run, but not saved Powershell scripts. This is the default setting.
AllSigned: Scripts can run, but must have a digital signature even if written on the local computer. Prompts you before running scripts from trusted publishers.
RemoteSigned: Scripts written on the local computer do not need a digital signature, but any script downloaded from outside (email, IM, Internet) must have a signature to execute.
Unrestricted: Any script can run, but scripts downloaded from outside will run with a warning.
If you’re working on a desktop and just experimenting with PowerShell, the best is to set the policy-level to Unrestricted. This allows you do everything with annoying security boundaries. Just be careful not to run every script you download from the internet 
If you’re working in a production environment and only want to run self-written scripts, the RemoteSigned level should be loosy enough.
Resolution :-
——————–
To change the Execution Policy to Unrestricted, type the following command in Powershell
Set-ExecutionPolicy Unrestricted
To change the Execution Policy to RemoteSigned (to run your own scripts), type the following command in Powershell
Set-ExecutionPolicy RemoteSigned
And that’s it! Your scripts can be run. Have fun !!!!!!!
Posted in Exchange Server 2010 Posts | 2 Comments »
Exchange 2010 Unable to start EdgeSync service on Hub Transport server
Posted by viralr on November 12, 2011
Exchange 2010 HT/CAS/MB on Windows Server 2008 R2 x64
When i try to start edge sync service on HT server, i get an error
1) Event Id 1070
“EdgeSync has failed. See the EdgeSync Log for more details.” and
2) Warning Event Id 1045
Initialization failed with exception: Microsoft.Exchange.EdgeSync.Common.EdgeSyncServiceConfigNotFoundException: Couldn’t find EdgeSync service configuration object for the site PDO-GKL. If the configuration object doesn’t exist in the Active Directory location CN=EdgeSyncService,CN=PDO-GKL,CN=Sites,CN=Configuration,DC=pdosolutions,DC=net, create it using the New-EdgeSyncServiceConfig cmdlet. If the object does exist, check its permissions.. If this warning frequently occurs, contact Microsoft Product Support.
Resolution :
1) Open Exchange power shell
2) Run command “New-EdgeSyncServiceConfig”
3) After that I was able to start the EdgeSync.
Hope this helps.
Posted in Exchange Server 2010 Posts | 2 Comments »
Exchange 2007 Error updating public folder with free/busy information on virtual machine,The error number is 0x8004010f.
Posted by viralr on November 4, 2011
Problem Description : Event Id 8207 is frquently occurring on the server :-
—————————————————————————————————-
Error updating public folder with free/busy information on virtual machine,The error number is 0x8004010f.
Resolution :-
——————–
1) For Outlook 2003 user make sure you have OAB public folder under system folders,use the following procedure to create OAB public folder
1) Open Powershell
2) Run the command
Get-PublicFolder “\non_ipm_subtree\schedule+ free busy” –recurse |fl name,*rep*
3) Found “First Administrative Group” replica is missing ,this replica is needed for old outlook 2003clients
PS] C:\Windows\System32>Get-PublicFolder “\non_ipm_subtree\schedule+ free busy”
-recurse |fl name,*rep*
Name : SCHEDULE+ FREE BUSY
LocalReplicaAgeLimit :
Replicas : {}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
LocalReplicaAgeLimit :
Replicas : {}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
Name : EX:/o=YourORGNAme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
4) To resolve this issue run the following command
new-publicfolder -name “EX:/o=YourORGNAME/ou=First Administrative Group” -path “\non_ipm_subtree\schedule+ free busy”
Note : ”EX:/o=YourORGNAME (Please change this value to your organization Name ,you will get your organization name from above command)
5) Make sure you have now First Administrative Group” replica as per below results ………………
Get-PublicFolder “\non_ipm_subtree\schedule+ free busy” –recurse |fl name,*rep*
[PS] C:\Windows\System32>Get-PublicFolder “\non_ipm_subtree\schedule+ free busy”
-recurse |fl name,*rep*
-recurse |fl name,*rep*
Name : SCHEDULE+ FREE BUSY
LocalReplicaAgeLimit :
Replicas : {}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
LocalReplicaAgeLimit :
Replicas : {}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
Name : EX:/o=YourORGNAME/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
Name : EX:/o=YourORGNAME/ou=First Administrative Group
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
LocalReplicaAgeLimit :
Replicas : {Public Folder Database}
ReplicationSchedule : {}
UseDatabaseReplicationSchedule : True
If the above steps does not resolve the issue,then check the following points………….
-Outlook 2007 uses Autodiscover and OAB virtual directory to download the OAB.
-From EMC make sure you have OAB Web based distribution enabled
-On Exchange 2007 under Program file>Microsoft>Exchanhe server you have ExchangeOAB folder which is shared (this will be -created if 2007 server is generating OAB)and you will see a folder inside it with guid value.
-In CAS server Restart Microsoft Exchange file distribution service.
-In CAS server open IIS and check for OAB virtual directory and see if there is any folder un it (guid value).Make sure Autodiscover and OAB URL are set correctly,to set the URL follow KB http://support.microsoft.com/kb/940726
-From EMC make sure you have OAB Web based distribution enabled
-On Exchange 2007 under Program file>Microsoft>Exchanhe server you have ExchangeOAB folder which is shared (this will be -created if 2007 server is generating OAB)and you will see a folder inside it with guid value.
-In CAS server Restart Microsoft Exchange file distribution service.
-In CAS server open IIS and check for OAB virtual directory and see if there is any folder un it (guid value).Make sure Autodiscover and OAB URL are set correctly,to set the URL follow KB http://support.microsoft.com/kb/940726
–Hope this post helps to resolve 8207 issue.
Refrence :
Posted in Exchange Server 2007 Posts | 1 Comment »
Services for Exchange Server 2007 or Exchange Server 2010 cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server
Posted by viralr on October 31, 2011
When you install Microsoft Exchange Server 2007 or install Microsoft Exchange server 2010 on a global catalog server, Exchange Server services cannot start. However, you can start other services manually. Servers in this configuration may take a long time to shut down. Additionally, the following events are logged:
Event ID : 1005
Source : MSExchangeSA
Category : General
Type : Error
Description : Unexpected error The Local Security Authority cannot be contacted ID no: 80090304 Microsoft Exchange System Attendant occurred.
Event ID: 2601
Source: MSExchange ADAccess
Category: General
Type: Warning
Description: Process MSEXCHANGEADTOPOLOGY (PID=1624). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…> – Error code=80040934. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Event ID: 1121
Source: MSExchangeIS
Category: General
Type: Error
Description: Error 0x96e connecting to the Microsoft Active Directory.
Event ID: 5000
Source: MSExchangeIS
Category: General
Type: Error
Description: Unable to initialize the Microsoft Exchange Information Store service. – Error 0x96e.
Cause :
———-
This problem occurs because the domain controller and other Exchange-Server-dependent services do not start completely when Exchange Server 2007 or Exchange Server 2010 try to start.
Solution :
————
–The solution which was worked for me was :
Set all the Exchange failing services to “Automatic (Delayed Start)” and reboot the server .
Make sure after setting the services to “Automatic (Delayed Start)” the services are not starting automatically after reboot.
Automatic (Delayed Start) delays the startup of a service approximately 2 min. after the system has completed starting the operating system.
More about “Automatic (delayed start)”:
Posted in Exchange Server 2010 Posts | Leave a Comment »
Outlook 2010 Sync Issues and Conflicts when Blackberry server available
Posted by viralr on October 20, 2011
–While troubleshooting this issue i observed some e-mails in conflicts folder under outlook 2010
Cause :
——-
–The issue happens because the user opens the message in Outlook before BES delivers it to their Blackberry. Then the message gets delivered to their mobile and thus the properties of the message on the server are changed before the user changes them with Outlook.
–Research the web and found following Blackberry forum
http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB19222
–As per this blackberry forums ,This is by design of Cached Exchange Mode in Microsoft Outlook. When a new email message arrives at the mailbox, Microsoft Outlook is notified before the BlackBerry Enterprise Server. When the BlackBerry Enterprise Server accesses the email message, it modifies properties such as injecting a RefID.
–A possible workaround is to enable the ProcessMailDelay registry key to cause the BlackBerry Enterprise Server to wait for a period of time before picking up the email message.
Resolution :
————
–To fix the sync issues, We have two options,
1) Disabled Cached Exchange Mode on user machine and see if that helps.
OR
2) On the Blackberry server follow the above blackberry forum and enable the “ProcessMailDelay” registry key to cause the BlackBerry Enterprise Server to wait for a period of time before picking up the email message.(This registry needs to be change from server so get this enable from your end)
Ref Article :
http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB19222
Hope this post helps to resolve Sync Issues and Conflicts.
Posted in Exchange Server 2010 Posts | Leave a Comment »
Finding cause of Exchange database dismount
Posted by viralr on October 5, 2011
Finding cause of Exchange database dismount :-
Question :
———–
Hi
Running Exchange 2007 SP2. This afternoon, noticed that one of our stores was dismounted….not sure when it happened, and becuase it’s a Sunday no one called our Helpdesk luckily. Could have been down since Friday PM.
I’d like to find out the cause, but our Event Logs are full of stuff – does anyone know what Event ID I’d be looking for etc? Any other way to find out when it was dismounted? I thought about checking the transaction logs but they have all been purged after the backup.
ANS :
—–
Please check the event viewer thoroughly for the following evnets
Event Id – 9539 & 9175 will be generated during store dismount ,
Event Id 482 will generate in case if the exchange store is dismounted due to low disk space.
Event Id 9688,89,90 will generate in case your database has exceeds the limit ,
Also which software are using for Exchange Backup ,do you have any scheduled task to dismout the store ?
Posted in Exchange Server 2007 Posts | 1 Comment »
What is the Exchange Server Dial-Tone server scenario?
Posted by viralr on October 5, 2011
# What is the Dial-Tone server scenario?
If you one day are faced with a relatively large corrupt Mailbox Store, restoring it can, depending on things such as backup hardware, backup application and network speed, be quite time consuming. Now the last thing you want to deal with in such a situation is frustrated users (or even worse a yelling CEO!).
So how can you get your users to calm down (and your CEO to s… up) and get back to work while you concentrate on getting the Mailbox Store back to life? There’s one simple answer and that is, you can create a dial-tone database and thereby get message flow and mailbox access recovered almost instantly. By using a dial-tone database your users can start to receive and send mail again, they can even go check out old messages that existed in their mailbox on the Exchange server (if their Outlook client has been configured to use cached mode that is), bear in mind though they have to switch between Online and Offline mode when prompted with the Outlook 2003 Exchange Recovery Mode dialog box. I’ll talk more about Outlook 2003 Recovery mode in “Demystifying The Exchange Dial-tone Restore Method (Part 2)”.
Using the dial-tone database restore method means that you, while restoring one or more corrupted Mailbox Stores from the most recent backup, have users connect to a new empty or blank Mailbox Store. The dial-tone restore method is by no means new; it’s been used with previous versions of Exchange as well, but now that we have the Exchange Server 2003 Recovery Storage Group (RSG) feature, the method becomes even more attractive when restoring Mailbox Stores within your Exchange messaging environment.
Note: With previous versions of Exchange a dedicated Exchange recovery server was required. Using a separate Exchange recovery Server meant you first had to restore the required Mailbox Store(s) or database to the recovery server, then either export the data from the restored database(s) to PST files using Exchange Server Mailbox Merge Wizard (ExMerge) or copy the whole Exchange database from the recovery server to the production server. As an Exchange database often is several gigabytes in size, this meant you typically had to copy large amounts of data over the wire which, depending on the network, could add several hours to the total recovery time.
Using the Recovery Storage Group feature makes it possible to restore Mailbox Stores without the need to build and use a separate Exchange Recovery Server; instead you can simply restore the Mailbox Store(s) directly to the Recovery Storage Group (RSG) on the respective Exchange Server or any other Exchange 2003 Server in the same Administrative Group. This makes it an easy and painless process to merge data from the restored Mailbox Store(s) to the dial-tone database, or swap the restored database from the Recovery Storage Group (RSG) to the dial-tone database in the original Storage Group, then merge data from the dial-tone database to the restored Mailbox Store. I’ll also talk more about swapping databases in “Demystifying The Exchange Dial-tone Restore Method (Part 2)”.
Note: If you’re not familiar with the Recovery Storage Group (RSG) feature, I recommend you checkout MS KB article: 824126 – How to use Recovery Storage Groups in Exchange Server 2003 which does a great job explaining how you can recover Mailbox Stores or individual mailboxes using by restoring a Mailbox Store to the RSG.
Posted in Exchange Server 2003 Posts | Leave a Comment »
Event Id 1009 The license store for the client access licenses is not valid and could not be restored from an automatic backup.
Posted by viralr on October 5, 2011
Event Id 1009 The license store for the client access licenses is not valid and could not be restored from an automatic backup:-
Observed following Event Id 1009 is occurring on the server which states that :-
Open the SBS Server Management Consol -Click on Licensing and observed there are no license key available.
Resolution :-
- Open SBS Server Management Consol – Click on Licensing Tab.
- Click On Restore Licenses
3. Click on Next
4. Click on Browse Button
5. Select C:\WINDOWS\system32\Autolicstr.cpa
6.Click on Next Button
7. Click on Finish Button
8. Make sure License Code and Number of Licenses are now display on the SBS Licensing Consol
Hope this post may help you to restore the missing licenses.
Please feel free to letme know if you have any query’s.
Posted in Exchange Server 2003 Posts | Leave a Comment »
Exchange 2010 Store.exe using up RAM
Posted by viralr on September 9, 2011
Exchange 2010 Store.exe using up all the available RAM (High Memory Usage ) :
–In Exchange 2010 It is absolutely normal for Store.exe to grab as much RAM on the server as it can possibly get – as long as Store thinks it needs it to optimize performance. Store was written to do so. It does this as it wants to do as much stuff in memory as possible, without having to go to the slow page file.
–This is a feature, not a bug,Exch will use as much memory as it can for store.exe to optimize performance,another service runs and need some of the RAM itself then exchange will release some
–We can limit the amount of memory that Exchange uses by following the below steps to limit the store.exe process
1. Start ADSIEDIT.msc
2. Navigate to Configuration > Services > Microsoft Exchange > <”Organization Name”> Administrative Groups > <”Administrative Group”>, > Servers > <”Server Name”> > InformationStore 
3. Right-click InformationStore, and edit msExchESEParamCacheSizeMax. Set it it to the number of pages to maximize the Database Cache to. Note that Exchange 2007 works with 8 KB pages and Exchange 2010 with 32 KB pages!
4. Restart the Microsoft Exchange Information Store service for the change to become effective.
So, for instance, if you want to limit the Database Cache to 4 GB of an Exchange 2010 server, set msExchESEparamCacheSizeMax to 131072 (4 GB = 4.194.304 KB / 32 KB). If you want to limit the Database Cache to 2 GB of an Exchange 2007 server, set msExchESEparamCacheSizeMax to 262144 (2 GB = 2.097.152 KB / 8 KB).
Note that lowering these values may degrade performance, in terms of server performance as well as in terms of end-user experience. However, smaller organizations with a limited number of mailbox users may benefit because they don’t let Exchange claim significant amounts of memory which it will never use.
You can get more information from the following documents
Why is Exchange Store.exe so RAM hungry?
http://msexchangeteam.com/archive/2004/08/02/206012.aspx
http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache/
Note :-It is not recommended to set the “msExchESEParamCacheSizeMax” key to limit the memory usage ,but if you still want to limit the store.exe memory utilization then follow the above ADSIEDIT steps.
Posted in Exchange Server 2010 Posts | 5 Comments »
