unisom restless leg syndrome can phenergan casu higgups phenergan coupons unisom schlaftabletten what phenergan used for provigil cost per pill

Exchange

Exchange Server 2013 SP1

If your following my posts you may notices I touched on a bug with Exchange 2013 SP1 before even posting about this update. That’s because I started to write this and didn’t yet finish; better late than never; I guess!

The following enhancements have been made with the release of Service Pack 1 for Exchange 2013

  • Support for running Exchange 2013 SP1 on Server 2012 R2.
  • Support for Windows Server 2012 R2 Domain Controllers and Windows Server 2012 R2 Forest and Domain Functional Level.
  • MAPI over HTTP. More information on MAPI over HTTP here. Note that MAPI over HTTP requires Outlook 2013 SP1; you can download Office 2013 SP1 32-bit version here and the 64-bit version here.
  • DLP policy tips for OWA.
  • Add custom document types to DLP using fingerprinting technologies.
  • Cmdlet logging in Exchange Administrative Console.
  • Support for IP-less DAGs (on Windows Server 2012 R2).
  • S/MIME support.
  • Rich-Text editor for OWA.
  • Edge Transport server role.
  • Support for SSL Offloading.

Notice
Since the release of Microsoft Exchange Server 2013 Service Pack 1 (SP1), Microsoft has become aware of an issue that affects some customers who use transport agents that are provided by third-party OEMs. For more information about this issue and a supported fix, see the following Microsoft Knowledge base article:

2938053 Third-party transport agents cannot be loaded correctly in Exchange Server 2013

This service pack resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 2860242 HTML format is lost after saving as an MSG file in Exchange 2013
  • 2900076 Mailbox quota warning message uses an incorrect language in Exchange Server 2013
  • 2910199 “Reply all by IM” chat window displays seven recipients in Outlook Web App
  • 2913999 Meeting request body and instructions are lost in delegate’s auto-forwarded meeting request
  • 2918655 Microsoft.Exchange.Servicehost.exe crashes after you enable FIPS
  • 2918951 Users cannot access public folders after you upgrade to Exchange Server 2013 Cumulative Update 3
  • 2925281 Outlook connectivity issue if SSLOffloading is “True” in Exchange 2013
  • 2925544 Empty ExternalURL value for ActiveSync virtual directory after build-to-build upgrade of Exchange Server 2013
  • 2927708 Resource mailboxes that are created by EAC will not be updated by policies in Exchange Server 2013
  • 2928748 Default from delegate’s address in shared mailboxes in Exchange Server 2013
  • 2928803 Long server connection for Outlook after a database failover in Exchange Server 2013
  • 2930346 POP3 access does not work if the name of the resource mailbox differs from the user’s name
  • 2930348 Manual redirection occurs in Outlook Web App if External URLs in each site are the same
  • 2930352 Outlook Web App cross-site silent redirection does not work in Exchange Server 2013

Manually Remove Auto-Mapped Exchange Mailboxes

Beginning with Exchange 2010 then on to Exchange  2013. User who used the client Outlook 2007/2010/and 2013  had a new feature called automapping.

Automapping takes advantage of Exchange auto-discovery services to map mailboxes which  a user has “Full Access” permissions granted.

This is very helpful to the end user as he or she is no longer required to know or learn how to add additional mailboxes to Outlook.

The not so helpful side is when a users access is removed and a ghosted mailbox folder exists in Outlook that the user is unable to remove.  Attempts to close the mailbox result in a message that reads:

This group of folders is associated with an e-mail account. To remove the account, click the File Tab, and on the info tab, click Account Settings, Select the e-mail account, and then click Remove.

Thank’s but this doesn’t work.  In fact even on a a clean install of Outlook the user still has the ghost folders associated to their Outlook Client.

 

So to tackle this issue, I used ADSIedit.

  1. Open ADSIEdit (WinKey R to open Run and type adsiedit.msc)
  2. Connect to the Default Naming Context. (Click OK)
  3. Locate the mailbox that you once were granted Full Access Permissions and …
  4. Right-click on the object, view properties.
  5. Scroll down to MsExchDelegateListLinked attribute.
  6. Click Edit, select the User Object and click Remove your information.

 

Now give it a little time for the change to replicate out in our Active Directory, you will later find these folders to be gone.

To prevent this from occurring when adding mailboxes you could always run the following command to disable automapping:

Add-MailboxPermission -Identity user@jermsmit.com
-User admin@jermsmit.com -AccessRights FullAccess
-AutoMapping:$false

 

Update from the comments 6/5/2017:
To find the mailbox, you actually find the AD user account, under the OU=Domain Name, within ADSIEdit.  – Thanks ‘ splunch ‘ for the info.

Installing Cumulative Updates for Exchange Server 2013

Tonight’s “home work” Assignment:
Update  Companies Exchange 2013 to Cumulative Update 3

Purpose

  • Address many of the issues that existed in Cumulative Update 2.
  • Bring additional value to the company

Oh and some of the newly introduced features / enhancements should help also:

  • Usability improvements when adding members to distribution groups in the Exchange Administration Console (EAC)
  • Windows Azure AD Rights Management available for use for IRM protection in on-premises Exchange deployments
  • Improved administrator audit logging experience
  • Windows 8.1/IE 11 no longer require the use of OWA Light

To get the Exchange 2013 Cumulative Update 3 just click here

Here are some steps to keep in mind when / if you are preforming this update yourself.

Preparation Tasks

Like that of installing any updates get ready. Read about what your installing and know why you are installing it.

  • Download the Cumulative Update 3 Install – here is a link hope it still works, if not just go to the download center and download it to each exchange server.
  • Backup Active Directory – Exchange CU3  will modify your schema
  • Backup you existing Exchange  2013 server(s)
  • Backup your existing Exchange databases (data/log volumes)
  • Have documented info on anything that you may have customized; such as configurations.
  • If you use 3rd party add-on to exchange (GOD HELP YOU)
  • And if you have no idea of what your doing and not 100% confident then you should not proceed further – my advice

Preforming the update

Locate your downloaded package containing the Cumulative Update 3 and extract it.  Once completed run the Setup.exe

If your server is connected to the internet you will be asked if you can check for updates. It’s a good idea to do this.

 

When the update had completed its check click Next to continue. The setup will being to cop files. This will take some time. Once completed the setup will detect that you are installing an update to Exchange 2013

You will presented with the normal license agreement, and as always you will accept them so you can proceed with the install. Once you have done so the installer will check for existing and new prerequisites it needs to continue the installation

After the readiness checks have completed the setup process continues and this my friend will take a very long time. In my case it was about 1 hour and 30 minutes to complete.

 

The setup process saves the exchange configuration and removes all the previous exchange installation

It then copies the new installation files to the server, in addition to other files such a languages etc..

Closer to the end of the update it configures your services again

And when the setup has completed you are prompted to restart the server if required.  *please* restart your server as you would want to test to ensure all services start up as expected.

Congratulations you have just updated to Exchange 2013 Cumulative Update 3

Post Install Tasks

  • Review windows event logs on your Exchange server(s)
  • Review services
  • Review connectivity to Exchange – Outlook Web Access, Outlook Clients, Mobile Device Connectivity
  • Write up a summery of what you did to share with team members are supervising management types – I included my actual report at the end of this post.

 

My Summery:

I have completed the work on Exchange.
Completion time was 12:30 AM Saturday, January 18, 2014

Tasks Preformed before Update Process
• Exchange Server was shutdown to adjust memory resources
• Exchange Data & Log Volumes moved  to Volume Collection
• Volume Collection of Exchanges Data & Log Volumes were made into a full snapshot as part of a backup / rollback plan
• Exchange Server was also made into a snapshot for backup / rollback plan

Update Process
• After exchange was restarted, began the verification of  files
•  Started update process,  monitored resources during the upgrade
• Update ran for 2 hours from start to finish.
• Once update was completed, restarted exchange
• Upon resuming, verified services were started automatically and storage volumes were attached
• Inspected event logs for any errors.
• Tested connectivity with OWA, Mobile and Outlook access

 

Error FileAccessDenied (JET_errFileAccessDenied …)

I ran into the following message when running an operation on one of my Exchange databases: Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 10.79 seconds.

The operation’s I was attempting was an integrity check on a database (ESEUTIL /G database_filename.edb). When this failed with the error above. I verified that the database was dismounted and that my antivirus scanner was not locking the file.

It took me a little bit of time but I soon released that the temp file for the database would be on my system volume which did not have the space required to run this operation.

That said I ran the command again; this time specifying a location for the temp file. That command looks something like this:

ESEUTIL /G database_filename.edb /TE:\Mailbox\Temp\thisismytempfile.edb

Please note that there is no space used after the command switch /T

For more info on the ESEUTIL: http://support.microsoft.com/kb/192185

Freeware Active Directory, Exchange, Lync provisioning tool

I can’t wait to play with this free software called Z-Hire. Z-Hire is a employee provisioning that handles account creations in Active Directory, Exchange, Lync. With just a few simple clicks (one click) accounts for Active Directory, Exchange, and Lync will be created.

Z-Hire doesn’t just assist those account administrators with creating new accounts; It simplifies account closures. Z-Hire can even create accounts in Office 365 and SalesForce. So take a look at it. I am sure you will find it very useful. Best of all, its free.

Link to help info:

http://www.zohno.com/docs/Z-Hire_V4_Administration_Guide.pdf

http://www.zohno.com/docs/Z-Term_V4_Administration_Guide.pdf

Download Z-Hire from TechNet

 

System Requirements
– Windows 7 X64 w/ .NET 3.5 and .NET 4.0 (Domain Joined)
– Windows Server 2008 X64 w/ .NET 3.5 and .NET 4.0 (Domain Joined)
– Windows Server 2008 R2 X64 w/ .NET 3.5 and .NET 4.0 (Domain Joined)

Permission Requirements
– Ability to create Active Directory user
– Ability to create Exchange Mailbox
– Ability to create / enable Lync user

Supported Environments
– Active Directory (all versions)
– Exchange 2007 (all versions)
– Exchange 2010 / 2013 (all versions)
– Lync 2010 / 2013 (both Standard and Enterprise versions)
– Office 365 Cloud
– SalesForce CRM Cloud