Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

          

Error:

Setup cannot continue with the upgrade because the “beremote()” process has open files:
The error listed above is not something to really stress about.

Resolution:

If you running Symantec Backup Exec you will need to stop the services and then retry the checks, they should all pass and allow you to carry on with your installation.


Regards,,
Gaurang Patel

Step by Step Adobe Reader Enterprise Depolyment

Adobe Reader Enterprise Depolyment

 

The steps below are the ones I followed to distribute and configure Adobe Reader X in an enterprise environment

• Setup a distribution agreement for Adobe products http://www.adobe.com/mena_en/products/reader/distribution.html

• Download the latest Adobe Reader base release e.g. 10.1.0 as an msi file

• Download the latest Adobe Reader quarterly update e.g. AdbeRdrUpd1013.msp

• Download the Adobe Customization Wizard  X http://www.adobe.com/support/downloads/detail.jsp?ftpID=4950

• Place the Adobe Reader msi file and the msp patch file in a folder.  Create an empty file called Setup.ini in the folder containing the msi and msp.

• Run the Adobe Customization Wizard and load the Adobe Reader msi file.  Choose your installation options, e.g. removing the EULA prompt, disabling updates etc. and save the mst into the folder holding the installation files.

• Run the command below to silently install Adobe Reader, update it using the msp file and apply the customizations in the mst file.

• msiexec.exe /i “\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\AdbeRdr1010_en_US.msi” PATCH=”\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\AdbeRdrUpd1013.msp” TRANSFORMS=”\\%SERVER%\SoftwareDistribution\Packages\AdobeReader_X\Custom_Install.mst” /qn

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

SharePoint People Picker, Audiences And Active Directory Trusts

 

The following post covers issues I came across when configuring SharePoint 2010 to work with an Active Directory (AD) trust.  In this scenario, SharePoint and user accounts are in domain A and a two-way transitive trust has been created with domain B.  Domain B holds news users who need access to SharePoint.
The first issue was the error below, which occurred when setting permissions for AD users and groups from domain B using the People Picker.

“No exact match was found. Click the item(s) that did not resolve for more options“

As a two-way trust exists between the two domains and the web application is using Windows authentication, SharePoint should have been able to locate users and groups in the trusted domain.  However, this wasn’t the case and I had to run the commands on this page http://technet.microsoft.com/en-us/library/cc263460.aspx.  The STSADM –o setapppassword –password <password> command has to be run on every SharePoint server running the Windows SharePoint Services Web Application service.  The stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv <list of forests or domains> -url <webapp> command is run on one SharePoint server running the Windows SharePoint Services Web Application.
The next issue occurred when using the Audience Picker to set an audience on a web part for a group from domain B.  Unlike the People Picker which queries AD, the Audience Picker queries the user profile database for imported users.  In this case I was able to search for the security group from the trusted domain, the group was listed as containing members, but the audience setting failed to work.  This error was caused by a mismatch between the NETBIOS name of domain B and the FQDN, e.g. the NETBIOS name was DOMAINB-XY and the FQDN was DOMAINB.COM.  In order to fix the problem I followed the steps listed here http://blogs.msdn.com/b/russmax/archive/2010/03/20/sharepoint-2010-provisioning-user-profile-synchronization.aspx.  The basic steps are:

1. Ensure Grant Replicate Directory Changes has been correctly assigned on domain B http://technet.microsoft.com/en-us/library/hh296982.aspx
2. Set the NetBiosDomainNamesEnabled property to true for the User Profile Service Application
3. Delete and recreate the AD connection within SharePoint for the import of users from domain B
4. Import users from domain B.

exchange spam filterexchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

 

If you want to upgrade a server running Windows Server 2008 R2 Standard to either the Enterprise, or Datacenter editions, it’s possible to do so online, without re-installing Windows.

Suggested Method will not disturb your existing Windows installation or applications installed on previous version.

Here i will show you the step by step upgradation of windows standard to datacenter edition, if you want to upgrade to Enterpise edition than just use "ServerEnterprise" insted of "ServerDataCenter" with Enterprise Product key as mentioned below product key table.

So are you ready to upgrade??? let's Start...

Open command prompt with run as Administrator rights and type DISM /Online /Get-CurrentEdition.  This will return the current Windows version.

Type DISM /Online /Get-TargetEditions to list the Windows editions to which this server can be upgraded.

If you type DISM /Online /Set-Edition:ServerDataCenter you’ll get the message in the screenshot below.  This is because even if you’re using a KMS server for internal activation, you have to provide a product key.  Fortunately, Microsoft have a page that lists the KMS client setup keys http://technet.microsoft.com/en-us/library/ff793421.aspx.  On this page you can find keys for Windows Server 2008 R2 Enterprise and Datacenter.

Typing DISM /Online /Set-Edition:ServerDataCenter /ProductKey:xxxxxx will upgrade the operating system.  All that’s required to complete the upgrade is a reboot.

 

Please find below Upgradation keys for diffrent possible versions, i recommend you to use Any time Upgrade for Client OS.

Platform	Operating system edition	Product key
Windows 7 and Windows Server 2008 R2
Client				Windows 7 Professional	FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Client				Windows 7 Professional N	MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Client				Windows 7 Professional E	W82YF-2Q76Y-63HXB-FGJG9-GF7QX
Client				Windows 7 Enterprise	33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Client				Windows 7 Enterprise N	YDRBP-3D83W-TY26F-D46B2-XCKRJ
Client				Windows 7 Enterprise E	C29WB-22CC8-VJ326-GHFJW-H9DH4
Server				Windows Server 2008 R2 Web	6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Server				Windows Server 2008 R2 HPC edition	TT8MH-CG224-D3D7Q-498W2-9QCTX
Server				Windows Server 2008 R2 Standard	YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Server				Windows Server 2008 R2 Enterprise	489J6-VHDMP-X63PK-3K798-CPX3Y
Server				Windows Server 2008 R2 Datacenter	74YFP-3QFB3-KQT8W-PMXWJ-7M648
Server				Windows Server 2008 R2 for Itanium-based Systems	GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Vista and Windows Server 2008
Client				Windows Vista Business	YFKBB-PQJJV-G996G-VWGXY-2V3X8
Client				Windows Vista Business N	HMBQG-8H2RH-C77VX-27R82-VMQBT
Client				Windows Vista Enterprise	VKK3X-68KWM-X2YGT-QR4M6-4BWMV
Client				Windows Vista Enterprise N	VTC42-BM838-43QHV-84HX6-XJXKV
Server				Windows Web Server 2008	WYR28-R7TFJ-3X2YQ-YCY4H-M249D
Server				Windows Server 2008 Standard	TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Server				Windows Server 2008 Standard without Hyper-V	W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
Server				Windows Server 2008 Enterprise	YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Server				Windows Server 2008 Enterprise without Hyper-V	39BXF-X8Q23-P2WWT-38T2F-G3FPG
Server				Windows Server 2008 HPC	RCTX3-KWVHP-BR6TB-RB6DM-6X7HP
Server				Windows Server 2008 Datacenter	7M67G-PC374-GR742-YH8V4-TCBY3
Server				Windows Server 2008 Datacenter without Hyper-V	22XQ2-VRXRG-P8D42-K34TD-G3QQC
Server				Windows Server 2008 for Itanium-Based Systems	4DWFP-JF3DJ-B7DTH-78FJB-PDRHK

error: Your request can't be completed right now. Please try again in a few moments.

error: 2013 Your request can't be completed right now. Please try again in a few moments.

I have setup Microsoft Exchange 2013 on windows 2012 Standard server operating system with Clean installation without any error. 

 

After installation I did many configuration and Testing than decided to Fully update the Exchange server as well as windows 2012 server. 

 

I found two update of Microsoft Exchange 2013 standard server on Microsoft TechNet

Cumulative Update 1 and 2

 

if you download Cumulative update 2 than no need to download CU1 because CU2 includes the CU1.

 

Cumulative Update file has very large size 1.3 GB which can be downloaded from below URL.

 

http://www.microsoft.com/en-us/download/details.aspx?id=39609

 

http://blogs.technet.com/b/exchange/archive/2013/07/09/released-exchange-server-2013-rtm-cumulative-update-2.aspx

                                                      
After Applying exchange Cumulative Update I landed with new error and not able to open Exchange Control Panel configurations.

 

Error:  

 

error: Your request can't be completed right now. Please try again in a few moments.

 

I was wondering why this problem occurred after updating the exchange server earlier it was working fine without any error, in a resolution I search a lot on a website but couldn't find proper solution than I recall the configuration did earlier before updating the server and found one clue and resolved my problem.

 

Cause :

 

Invalid site binding entry in Exchange Back End website

 

Resolution :

 

1) open Administration Tools

2) open IIS

3) Nevigate to exchange back end website

4) Click on Site Binding

5) Remove user defined Site binding.

 

6) Restart IIS / Restart server

7) you are Done!!!!

 

 

This solution works in my case !!!!

 

 

Regards,,

Gaurang Patel

 

 

 

Windows Server Backup failed to backup with error 0x81000101

            

Windows Server Backup failed to backup with error 0x81000101

        

Symptom:

 

Sometimes Windows Server Backup failed to backup the data. The error is:

The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again.

In the event viewer, found the following error:

The backup operation that started at '‎**** has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Cause:

Windows Server Backup is timing out during shadow copy creation since it is taking more than 10 minutes.

Resolution:

- Run regedit.exe and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP"

- Create a new Registry value of type DWORD with name "CreateTimeout"

- Change value to 12000000(2*10*60*1000 = 20 mins) in decimal

More information:

http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx

System State Backup Failed on Windows 2008 R2 SP1 with Windows Backup

Dear All,
I am running Windows Server 2008 R2 SP1 Domain Controller and have a scheduled job to backup only the System State data to a volume (D drive) on the server itself.

 Periodically and randomly the job fails with a status message in the Windows backup console saying "Failed. The operation was stopped. Detailed error: Access is denied"

In the event log I see the following

I checked online for the above error code and found MS Hotfix 2182466 but when I try to install it, it says "The update is not applicable to your computer" (I have verified the hotfix is the correct one for the server I am running).

Resolution :

After searching a lot on internet and suddenly I found solution.

TrendMicro Antivirus Software is installed on server so that I have disabled it and bOOOOOMMMMM!!!!!!!! windows  system state backup has completed without any error...

 

Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

 

In my hotel room in Orlando, getting ready for an Exchange 2007 transport presentation tomorrow morning at TechMentor. When trying to telnet to the SMTP port of an Exchange 2007 Hub Transport server, I got the following error:

452 4.3.1 Insufficient system resources

Not a good thing the night before a presentation – Murphy’s law at work again!
The Application Event Log has Event ID 15002 from MSExchangeTransport saying “The resource pressure is constant at High. Statistics… “. The event goes on to tell you that inbound mail submission has stopped, and it’s due to disk space being low on the volume where the queue database is located.

Figure 1: Event ID 15002 logged by MSExchangeTransport
Exchange Server 2007 transport queues are not the familiar .eml files you see in Exchange Server 2003/2000, which reside in the \mailroot\vsi <1>\queue folder (<1> is the instance number of the SMTP virtual server) on the file system. Yes, transport queues have been moved to a JET database of its own.

What’s Back Pressure?

In Exchange Server 2007, the Transport service monitors system resources such as disk space and memory on Transport servers (the Hub Transport and the Edge Transport servers), and stops message submission if it’s running low on these resources. It continues to deliver existing messages in the queue. When resource utilization returns to normal, it resumes message submission. The feature is called Back Pressure.
In this case, Exchange required 4 Gigs of free disk space on the volume where the Queue database was located – I had about 3.95 Gigs. :)

Changes to Back Pressure settings in Exchange Server 2007 SP1

The Back Pressure settings in Exchange Server 2007 RTM stop inbound mailflow if free disk space is below 4 Gigs. This static threshold has been lowered in SP1 to a more realistic 500 MB.

The Resolution

Many configuration options for transport servers are saved in an XML file named EdgeTransport.exe.config (it’s the same file name on both server roles— Edge Transport and Hub Transport) located in \Exchange Server\Bin\.
To get transport to resume submissions, you can use any of the following methods. All of the following require you to edit the EdgeTransport.exe.config file.

1. Disable BackPressure: Although Microsoft doesn’t recommend it, it does provide a way to Disable Back Pressure
2. Tweak BackPressure thresholds: Modify BackPressure parameters to more accurately define what’s high utilization for your deployment or server configurations, as explained in the above docs.
3. Move the queue database to another volume: Another resolution, and the one I used in this case, was to move the queue database to another volume with ample of free space, using the following procedure:
   1. Add the following key in the <AppSettings> section in EdgeTransport.exe.config, as documented in “How to Change the Location of the Queue Database“:
      
      <add key=“QueueDatabasePath” value=”D:\Queue\QueueDB” />
   2. Save the file and restart the Microsoft Exchange Transport service from the Services console or by using the Restart-Service cmdlet (Restart-Service MSExchangeTransport).

Message submission resumes.

how to increase Virtual Processor ( vCPU) in Hyper-v Guest OS

Hi,

here I will show you how to increase Virtual CPU for particular Hyper-V guest OS, basically hyper-v (windows Server 2008 R2 Sp1 )Supports only 4 Virtual CPUs which is a limitation of Hyper-V, the limitation of Hyper-v is described on below TechNet article.

http://technet.microsoft.com/en-us/library/ee405267(WS.10).aspx

So if you want to increase Virtual CPU of the GUST please follow below Steps.

1) Shutdown all Virtual Servers.

2) Stop All Hyper-V Services ( services.msc)

3) Open Hyper-V data Store where GUEST server .VHD is stored.

4) Open Virtual Machine Folder and edit .xml file.

5) Edit below parameter in .xml File.

<processors>
<count type=”integer”>8</count><features>
< limit type=”bool”>False</limit>
< /features>
< limit type=”integer”>100000</limit>
< limit_cpuid type=”bool”>False</limit_cpuid>
< reservation type=”integer”>0</reservation>
< weight type=”integer”>100</weight>
< /processors>

6) Save and Close the file.
7) Start Hyper-V Services.
8) Start Guest server.
9) Check the Processor ( you need to restart )
10) Done!!!!


Note : 1) Physical host should have enough core to support more cores for Ex: Physical server has only 4 Core and you want to assign 6 core then it won't work.

2) this is a work around solution so please take care before making change in production environment.

3) for more information please follow http://social.technet.microsoft.com/Forums/en-US/virtualmachingmgrhyperv/thread/cf17b31f-3ef9-49c8-93a0-a6d6b83b2bbe



regards,,
Gaurang

step by step installation of Microsoft Exchange 2013

Hello Friends,

i will show you how to setup Microsoft Exchange 2013 server, First of all i would like to show you the Compatibility matrix of MS Exchange 2013 as mentioned below.

Note: Once you install / Prepare AD for MS Exchange 2013 you won't be able to install MS Exchange 2010 or later version.

Operating System Requirement:

Operating system

• Windows Server 2012
• Windows Server 2008 R2 Standard with SP1
• Windows Server 2008 R2 Enterprise with SP1
• Windows Server 2008 R2 Datacenter RTM or later

Operating system for Management Tools (on a computer with 64bit processor)

• Windows Server 2012
• Windows Server 2008 R2 Standard with SP1
• Windows Server 2008 R2 Enterprise with SP1
• Windows Server 2008 R2 Datacenter RTM or later
• 64-bit edition of Windows 8 Release Preview
• 64-bit edition of Windows 7 with SP1

Active Directory Server Requirement:

Schema Master

In each Active Directory site where you plan to install Exchange 2013 Preview, you must have at least one writable domain controller running any of the following:

• Windows Server 2012
• Windows Server 2008 R2 Standard or Enterprise SP1 or later
• Windows Server 2008 R2 Datacenter RTM or later
• Windows Server 2008 Standard or Enterprise SP1 or later (32-bit or 64-bit)
• Windows Server 2008 Datacenter RTM or later

Schema Master

• Windows Server 2012
• Windows Server 2008 R2 Standard or Enterprise
• Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
• Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
• Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Global Catalog Server

At least one Global Catalog server in every Active Directory site where you are planning to install Exchange Server 2013 Preview on,

• Windows Server 2012
• Windows Server 2008 R2 Standard or Enterprise
• Windows Server 2008 R2 Datacenter RTM or later
• Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
• Windows Server 2008 Datacenter RTM or later

Active Directory Forest

• Active Directory must be at Windows Server 2003 forest functionality mode or higher.

Prerequisites for Windows 2008 R2 SP1:

Required Windows roles and features

1. Open Powershell (Open Powershell window with elevated rights by right-clicking it "Run as Administrator") and import server module first with "Import-Module ServerManager" command then install/enable Operating System components as per below;
   
   Client Access and Mailbox role
   Import-Module ServerManager
   Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Required Software

1. Microsoft .NET Framework 4.5 RC
2. Windows Management Framework 3.0
3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
4. Microsoft Office 2010 Filter Pack 64 bit
5. Microsoft Office 2010 Filter Pack SP1 64 bit
6. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
7. KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)
8. KB2533623 (Insecure library loading could allow remote code execution)

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64)
(Control Panel -> Programs and Features -> Uninstall)

Register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS)
Open CMD
Run this command:
%SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable

Restart the IIS services:
IISReset

Windows Server 2012 prerequisites

1. Open Powershell (Open Powershell window with elevated rights by right-clicking it "Run as Administrator") and import server module first with "Import-Module ServerManager" command then install/enable Operating System components as per below;
   
   Client Access and Mailbox role
   Import-Module ServerManager
   Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Required Software

1. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
2. Microsoft Office 2010 Filter Pack 64 bit
3. Microsoft Office 2010 Filter Pack SP1 64 bit

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64)
(Control Panel -> Programs and Features -> Uninstall)

Prepare Schema and AD

Prepare the Active Directory Schema to install Exchange Server 2013 (basically this will extend the schema). You will have to insert the Exchange Server 2013 RTM DVD (Media Kit)

– Assumption, DVD ROM drive letter is D:\ and Exchange Server Installation Setup path is D:\Setup.exe –

• Open PowerShell or CMD in admin mode

D:\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Or

D:\Setup.exe /PS /IAcceptExchangeServerLicenseTerms

• Now that the Schema is being prepared, we will have to move on to the next step and prepare the Active Directory Topolgy.

Before you run this command you should have your Exchange Server 2013 Organization name

D:\Setup.exe /PrepareAD /OrganizationName:<name> /IAcceptExchangeServerLicenseTerms

Or

D:\Setup.exe /PAD /OrganizationName:<name> /IAcceptExchangeServerLicenseTerms

Now that the Schema and the AD are prepared,

Run the Exchange Server Setup from the DVD (Run as Administrator)

 

It will request to check for updates, select Connect to the internet and check for updates and click next

 

 

necessary updates will be downloaded , in my case there was no updates

 

 

Files are being copied to install Exchange Server 2013

 

 

Initializing the Exchange Server 2013 Setup

 

 

Gives and Introduction to the Exchange Server 2013, upon reading click next 

 

Accept the License Agreement (you are supposed to read this) and click next

 

 

I will have left the default setting of selecting the “Use Recommended Settings” option and click next

 

 

The Server roles that are to be installed select and click next. Notice that Exchange Server 2013 does not contain all the server roles that were introduced in Exchange 2007 and 2010. It has been reduced to 2 now (to read more click here)

 

 

The path of the installation and the required space for the installation. click next upon making the changes

 

 

Malware Protection Settings – I am leaving it on – default setting and click next

 

 

Readiness check – whether your server is ready for Exchange 2013, click install once done

 

 

Installation begins and it has 14 steps. It will take some time

 

 

Setup completion, read and click finish.

 

 

Exchange Server 2013 program shortcuts on Windows Server 2012. Note that the Exchange Management Console (EMC) is no where to be seen. This is because the traditional EMC is being moved to a web interface

https://servername/owa

Log in page for the Web Based Exchange Admin center (Equivalent to EMC). login using your admin credentials

Log in to the Exchange Control Panel.

https://<Exchange Server FQDN/IP>/ecp
https://localhost/ecp