Custom Technology Solutions, Inc

Corporate Blog

Custom Technology Solutions, Inc - Corporate Blog

Windows Server 2012 R2 Essentials Migration – Keys to Success

[Today's post comes to us courtesy of Ajay Sarkaria, Rituraj Choudhary, Harshal Charde and Sandeep Biswas from Global Business Support] The purpose of this post is to help you successfully migrate from a previous Windows Server SKU, Small Business Server SKU, or a Windows Server Essentials SKU current in Product Lifecycle to Windows Server 2012 R2 Essentials. If your business has up to 25 users and 50 devices, you may migrate to Windows Server 2012 R2 Essentials. If the count extends up to 100 users and 200 devices, to use the features empowered by Windows Server Essentials role, you must migrate to the Standard or Datacenter editions of Windows Server 2012 R2 and install the Windows Server Essentials Experience (ServerEssentials) role. The content on this blog extends from the content found at Prepare your Source Server for Windows Server 2012 R2 Essentials migration . Use the following annotated checklist to keep you on track. 1. Read through the Migration Guide before starting. Understand what setup will do for you and what you need to do manually. 2. Get hands-on experience with our Technical Training Series. Windows Server 2012 R2 Essentials technical training series now available on Microsoft Virtual Academy . 3. Join the Windows Server Essentials Forum . You might find an answer to a question you have, seek advice on your migration plan, or simply see what others have encountered that you might not have considered. 4. Practice a migration yourself in a test environment. This way you know what to expect. This also allows you to test the hardware and verify you have the necessary BIOS updates and drivers. 5. On the Source server, run the Best Practices Analyzer(s). Run the Best Practice Analyzer for the respective components, whether you are migrating from Windows Server or Windows Server Essentials or Small Business Server. Make sure to allow the BPA to get updates when first launching. Resolve any issues reported in the source environment ahead of time. Do not ignore Warnings as they might impact the migrations too. Know that SBS 2003 SP 1 is not the same as Windows 2003 SP 1 or SP 2. If you're migrating from Windows Small Business Server 2003 or Windows Server 2003, delete the Log on as a service account setting from Group Policy. 6. Plan your Messaging Deployment options. If your source domain has Exchange Server installed, depending on the source Exchange Server version, you will have to plan the future deployment of Exchange Server or Office 365. Windows Server 2012 R2 Essentials supports integration of On-Premises Exchange server or an Integration with Office 365 Subscription. Compare Office 365 for business plans 7. On the Source server, make sure the Active Directory is healthy. If there is only one DC, make sure the SYSVOL and NETLOGON shares are present. Also, check the File Replication Service event log to see if it is in Journal Wrap. The event below is an example of what to look for. Event Type: Error Event Source: NtFrs Event ID: 13568 Description: The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR. If there are multiple domain controllers in the source environment, force an Active Directory replication between them in Active Directory Sites and Services and verify it is successful. You can also run the Microsoft IT Environment Health Scanner in the source environment to uncover any AD health issues. Microsoft IT Environment Health Scanner An unhealthy Active Directory can result in Windows Server 2012 R2 Essentials migration installation failure . 8. On the Source server, check the Primary group of the account you will use to install the Windows Server 2012 R2 Essentials server into the domain. Make sure the Primary group is set to something besides Domain Admins, Enterprise Admins, or Schema Admins. In the properties of the user account, click the Member Of tab, and at the bottom look for the Primary group. Make sure the Primary group IS NOT: Domain Admins or Enterprise Admins or Schema Admins. To change it, select Domain Users and click the Set Primary Group button. 9. Make sure the Admin account you are using for the migration has a STRONG password. Strong passwords must meet the following minimum requirements: Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters. Passwords must be at least six characters in length. Passwords must contain characters from three of the following four categories: English uppercase characters (A through Z). English lowercase characters (a through z). Base 10 digits (0 through 9). Non-alphabetic characters (for example, !, $, #, %). 10. Install the samsrv.dll update from KB 939820 on all Windows 2003 domain controllers in your environment, including the SBS 2003. 939820 Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: “No authority could be contacted for authentication” when you use Remote Desktop Connection . 11. Disable WSUS on Source domain prior to migration. If you have a deadline set for an update in WSUS that is past-due, your Windows Server 2012 R2 Essentials setup can fail when the update is automatically installed and the Windows Server 2012 R2 Essentials is rebooted. We recommend disabling WSUS on the source server for the duration of the migration. For this, on the source server, open IIS Manager, and stop the “ WSUS Administration ” site. 12. In the source domain, disable anything that may install software on machines added to the domain. Similar to the point above, your Windows Server 2012 R2 Essentials setup can fail if something outside of it initiates a server restart while it’s in the middle of its setup routine. Things to keep an eye out for: Logon Scripts Group Policy Remote Management Tools Devices like printers that may install a driver that requires a reboot. 13. Make a System State Backup of the source server. We recommend a full backup of the source, however at least a system state backup of the source server is required to recover from any failures that may be encountered during the migration. We recommend you use native Windows Server Backup. 14. Do not make any changes on the network. From now until the Windows Server 2012 R2 Essentials migration setup is complete, do not make any changes on the network. This is not a good time to be doing any of the following: Changing passwords Installing Software Removing Domain Controllers Changing out the network hardware Restoring servers Rebooting domain controllers Re-wiring the network 15. Check the “Log on as Batch job” user right assignment on the Default Domain Controllers group policy. Launch gpmc.msc Expand Forest, Domains, your domain, Domain Controllers, and select the Default Domain Controllers Policy. Click on the Settings tab and expand Computer Configuration, Policies, Windows Settings, Security Settings, Local Policies/User Rights Assignment. Find the “Log on as batch job” right, and make sure that you have an entry for BULTINAdministrators If you don't have that entry, do a right-click edit on top of the policy on the left pane, navigate to the location you just checked and edit the right to add the missing value. 16. Start the Migration Process Depending on the Target Operating System edition, Follow one of the below blogs: Deploying Windows Server 2012 R2 Essentials in an Existing Active Directory Environment Deploying Windows Server 2012 R2 Standard/Datacenter with Windows Server Essentials Experience role in an Existing Active Directory Environment On subsequent posts we will cover documentation and tips to help you recover if you have encountered an issue during or post migration.

Revisiting SBS 2011 Standard Migrations

We have been experiencing some good amount of volume around SBS 2011 Standard migrations recently. If you are stuck on one of such migration issues please start by following these outstanding yesteryear blogs: SBS 2011 Standard Migrations – Keys to Success SBS 2011 Standard Migrations – Keys to Success – Part 2: The Setup Phase SBS 2011 Standard Migration – Keys to Success – Part 3: Post Setup and Common Failures These blogs cover most of the migration scenarios and should help.

Secure Remote Access in Small and Midsize Businesses Solution Guide Now Available

[This post comes to us courtesy of Kumud Dwivedi from Content Publishing] If you are a small to midsize business that is looking for a reliable way to allow remote network users to access business data outside of your network, we now have a solution guide to address this. Windows Server 2012 R2 Essentials and Windows Server 2012 R2 provide a solution to securely access data when off-premises via a wide range of Internet-connected devices by using various methods such as Remote Web Access, virtual private network, or the My Server app. If your business has up to 25 users and 50 devices, use Windows Server 2012 R2 Essentials. For up to 100 users and 200 devices, use the Standard or Datacenter editions of Windows Server 2012 R2 with the Windows Server Essentials Experience role installed. To view this solution guide, see Secure remote access in small and midsize businesses .

Windows Server 2012 R2 Essentials technical training series now available on Microsoft Virtual Academy

[This post comes to us courtesy David Fabritius from Product Marketing] Have you been looking for in-depth technical readiness content on Windows Server 2012 R2 Essentials and the new Windows Server Essentials Experience role? In this comprehensive training series, we cover the gamut, from deployment options to the end user experience. Check it out at http://www.microsoftvirtualacademy.com/training-courses/windows-server-2012-r2-essentials , and get hands-on experience with our virtual lab, http://go.microsoft.com/?linkid=9836955 .

Deploying Windows Server 2012 R2 Essentials in an Existing Active Directory Environment

[This post comes to us courtesy of Rituraj Choudhary from Global Business Support] In this post we will discuss deploying Windows Server 2012 R2 Essentials in an existing Active Directory domain. Some key points to keep in mind in this scenario are: The Windows Server 2012 R2 Essentials once deployed, must be the domain controller at the root of the forest and domain, and must hold all the FSMO roles. Windows Server 2012 R2 Essentials can only be deployed into a single domain. Also, a read-only domain controller cannot exist in this domain. It can be installed in a pre-existing Active Directory domain only on the pretext that you are migrating to Windows Server 2012 R2 Essentials. Note that there is a grace period of 21 days for completing the entire migration from previous versions of Windows Server Essentials or Small Business Server editions. Note : If you are planning to deploy a Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter with Windows Server Essentials Experience role in an existing Active Directory environment, please follow our previous post . Here are the steps we need to cover for this deployment: Plan migration for LOB Applications Complete the initial setup of Windows Server 2012 R2 Essentials Rename the computer Make it a Replica Domain Controller Transfer all the FSMO Roles to the new Windows Server 2012 R2 Essentials Configure Windows Server Essentials Experience role Make required changes to the DHCP Scope Demote and remove Active Directory Domain Services from the source server Set up Windows Server 2012 R2 Essentials features Before beginning the deployment of Windows Server 2012 R2 Essentials in the existing domain, make sure you plan, rehome and reconfigure your Line of Business applications, so that they are available during and post migration, as per your business requirements. The first step towards the deployment of the Windows Server 2012 R2 Essentials in an existing domain is to complete the initial setup. Once the installation is complete and the server reboots, log on with the local administrator account. Important : When you log on to the server desktop, you will see Configure Windows Server Essentials wizard that gets triggered automatically. Click Cancel (1) to cancel this wizard at this time, and confirm the cancellation by clicking Yes (2) to the subsequent warning. Make sure you are connected to the local network. To double-check, you may ping the internal domain name to verify that it resolves to the IP address of the source domain controller. In most probability you would like to change the name of the server conventionally. Make sure to do that right now, if you intend to. The simplest way would be to open a PowerShell window as an administrator on the target Windows Server 2012 R2 Essentials and issue the following command: Rename-Computer *  is the new name of the local computer in the above command. For example: Restart the computer for the changes to take effect. Please note that the Configure Windows Server Essentials wizard will show up again and you need to cancel it. Confirm the new computer name by issuing command hostname on a PowerShell or a Command Prompt window. The next step is to add this Windows Server 2012 R2 Essentials to the domain as a replica domain controller. To accomplish this, open Server Manager . On the Server Manager Dashboard, click Manage , and then click Add Roles and Features . On the Add Roles and Features Wizard that shows up subsequently, proceed through by clicking Next on each of these pages: Before You Begin , Installation Type , and Server Selection with the default options selected. On the Server Roles page, click to select Active Directory Domain Services . This action pops up a new dialog to add some features. Click Add Features to add the features that are required for Active Directory Domain Services . Click Next on Features and AD DS (Active Directory Domain Services) pages, and Install on the Confirmation page. Once the installation is complete, click Close to close the wizard. Back on the Server Manager, click the Notifications flag, and click Promote this server to a domain controller to promote the server to a domain controller. This action should bring up the Active Directory Domain Services Configuration Wizard . On the Deployment Configuration page, select the option Add a domain controller to an existing domain , and then click Select… button next to the Domain field. You need to enter the domain administrator credentials here, so that it picks up the domain name that exists in the local network. Select the existing domain name here. Once you click OK , the Domain field should now populate with the FQDN of the domain name, e.g. contoso.local . Click Next . On the Domain Controller Options page, leave the default options selected, and enter a Directory Services Restore Mode (DSRM) password. Keep it safe so you won't lose it. Now click Next . Proceed on these pages with the default options selected: DNS Options , Additional Options , Paths , Preparation Options , and Review Options . On the Prerequisite Check page, after certain checks are validated, you will be presented with an option to install. Click Install to proceed. Note : After you click Install , the server would automatically reboot at the end of the promotion operation. PowerShell Script: We have put the GUI options on the blog post for better grasp and visibility by an end user. You may also choose this PowerShell Script over the GUI. Import-Module ServerManager Add-WindowsFeature AD-Domain-Services Import-Module ADDSDeployment Install-ADDSDomainController -NoGlobalCatalog:$false -CreateDnsDelegation:$false -Credential (Get-Credential) -CriticalReplicationOnly:$false -DatabasePath “C:WindowsNTDS” -DomainName ” contoso.local ” -InstallDns:$true -LogPath “C:WindowsNTDS” -NoRebootOnCompletion:$false -SiteName “Default-First-Site-Name” -SysvolPath “C:WindowsSYSVOL” -Force:$true ' * contoso.local is the domain name in this example ' * The server will reboot automatically to complete the operation After the reboot, you would be presented with the domain account to log in with since the server is joined to the domain at this point. After the logon, it will wind up the process of domain controller promotion. You can then verify the domain join and domain controller functionality on a PowerShell window as: Dir ENV:U* Import-Module ActiveDirectory Get-ADDomainController You would again see the Configure Windows Server Essentials wizard pop up. Let's minimize the wizard this time. Let us now transfer the FSMO roles to the new server. Check the current FSMO role holder domain controller using the command: netdom query fsmo These FSMO roles should be with your source server currently. Run the following commands on an elevated PowerShell window on Windows Server 2012 R2 Essentials to transfer all the FSMO roles on Windows Server 2012 R2 Essentials: Move-ADDirectoryServerOperationMasterRole –Identity 0,1,2,3,4 * is the name of the new Windows Server 2012 R2 Essentials in the above command. You can either say ' a ' once or ' y ' 5 times for each operation master roles transfer in the subsequent prompts. That is pretty much it. You may again run the netdom query fsmo command to verify that they are now with the new Windows Server 2012 R2 Essentials. Let us now restore the Configure Windows Server Essentials wizard from the Taskbar or Server Manager under Notifications, and click Configure on the Configure Windows Server Essentials page. This should take a few minutes. Click Close on the Results page after the configuration is complete. Change the scope options on the DHCP server on the existing domain to point to the new Windows Server 2012 R2 Essentials as the DNS server. Follow up by demoting the source server. The shortest way to accomplish this is to run the command Uninstall-ADDSDomainController on an elevated PowerShell window on the source server. Please note that this process reboots the server automatically to complete the operation. After the source server reboots, you may remove the Active Directory Domain Services role from the Server Manager on the source server. You are now ready to use your new Windows Server 2012 R2 Essentials. You may now proceed to add client PCs using the connect wizard so that it shows up in the DEVICES tab of the Windows Server Essentials Dashboard , set up Anywhere Access etc. and other Essentials features as per your requirement.

Top Support Solutions for Windows Small Business Server 2011 Standard

This is a collection of the top Microsoft Support solutions to the most common issues experienced using Windows Small Business Server 2011 Standard (updated quarterly). Note that some content that applies to earlier versions of Windows Server is listed, because it can be helpful with Windows Small Business Server 2011 Standard issues also. Solutions related to – Active Directory and Directory Services      Solutions related to – Client Computers issues      Solutions related to – Internet Information Services (IIS) Solutions related to – Licensing      Solutions related to – Mail flow issues Solutions related to – Network and Web Connectivity Solutions related to – Reliability and Performance Solutions related to – Small Business Server (SBS) Components      Solutions related to – Microsoft SQL Server      Solutions related to – Installation and Migration Active Directory and Directory Services Domain controller (DC) does not function correctly An update for the Windows Small Business Server 2011 Standard Migration Preparation Tool is available How to Clean Up Active Directory after an Unsuccessful Migration How to Perform an Authoritative System State Restore in SBS 2008/2011 Standard Debunking Myths About Additional Domain Controllers In SBS Domains An error occurred while promoting the server to a domain controller Cannot create the Active Directory structure required to create users, groups, and computer accounts for Windows Small Business Server 2011 Standard Catalog of Windows Small Business Server 2011 Standard Error Messages Using the BurFlags registry key to reinitialize File Replication Service replica sets Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller Distributed File Systems (DFS) or File Replication Service issues     DFS Replication: Frequently Asked Questions (FAQ) “Active Directory Replication is taking longer than expected” message stops SBS installation Using the BurFlags registry key to reinitialize File Replication Service replica sets How to Manually Create the Windows Small Business Server 2011 Standard and WSUS Group Policies Objects Restoring the SBS GPOs from a Different Server Group Policy does not apply GPO does not apply to a specific user or computer Troubleshooting Group Policy Using Event Logs Resultant Set of Policy (RSoP) Using Gpresult Local Security Authority Subsystem Service (LSASS) errors The Lsass.exe process crashes on Windows Server 2008 R2-based domain controllers Lsass.exe crashes and error code 255 is generated in Windows Server 2008 R2 or in Windows 7 Memory leak occurs in the Lsass.exe process on a domain controller that is running Windows Server 2008 R2 How to Troubleshoot High LSASS.EXE CPU Utilization on an Active Directory Domain Controllers   Client Computers issues     Folder redirection and Offline Files Folder Redirection in Small Business Server 2008 How to re-initialize the offline files cache and database in Windows XP How to Properly Disable Offline Files in Windows Vista Enable folder redirection on the Destination Server for Windows SBS 2011 Standard migration Redirect user account folders to the server Repair folder redirection and shared folders Delete the old folder redirection Group Policy object for Windows SBS 2011 Standard migration Change access to Folder Redirection for a user account Move settings and data to the Destination Server for Windows SBS 2011 Standard migration Folder Redirection fails to apply when redirected to mapped drive letter, instead of UNC path Folder redirection in Small Business Server 2008 Work Smarter with Offline Files and Shadow Copy On a Windows Vista-based or Windows 7-based client computer, you can still access offline files even though the file server is removed from the network You may encounter file corruption issues when you use the Offline Files feature to synchronize data in Windows 7 Roaming profiles How to Configure a Roaming User Profile Automatic creation of user folders for home, roaming profile and redirected folders. Configuring Roaming User Profiles Best Practices for User Profiles Roaming profile users experience slow logons on Windows 7 or Windows Server 2008 R2 client computers Managing Users, Groups, and User Profiles Roaming Profile Compatibility – The Windows 7 to Windows 8 Challenge Group Policy GPO does not apply to a specific user or computer Troubleshooting Group Policy Using Event Logs Resultant Set of Policy (RSoP) Using Gpresult Windows 7 Clients intermittently fail to apply group policy at startup Other Client Computers issues Why is My Computer Status Not Showing Online in the SBS Console? Why Does My SBS 2008 Premium Second Server Display as a Client Computer? Why Are Some of My Client Computers/Servers Not Displaying in the SBS Console? Unable to connect to Windows 7 SP1 client on a SBS 2011 Standard or SBS 2011 Essentials domain after it has been updated with RDP 8 update RWW Error on Vista and Windows 7 Clients Windows Small Business Server 2011 Standard Client Computer Help Set Up a VPN on Client Computers SBS 2011: Troubleshooting Client Deployment Accessing server resources Windows Small Business Server 2011 Standard Client Computer Help You experience a delay when you use your Windows XP computer to log on to a domain or to connect to a network resource Mapped Drive Connection to Network Share May Be Lost Joining the domain Automatically connect client computers to the network Remove a client computer from the network Windows XP/Vista Workstations Fail To Connect to SBS 2008 When Using Http://connect SBS 2011: Troubleshooting Client Deployment Users cannot access http://connect to join client computers to the domain Connecting Windows 8 to Small Business Server 2011 Standard after the Installation of the Latest Update Rollup 3 Slow domain logon Small Business Server 2011 Slow to Boot and Several Services Fail to Start You experience a long domain logon time in Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2 after you deploy Group Policy preferences to the computer Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7 You experience a delay when you use your Windows XP computer to log on to a domain or to connect to a network resource Long startup or logon time when no domain controllers are available on a Windows 7-based or Windows Server 2008 R2-based domain member computer Event ID 5719 is logged when you start a Domain Member You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles You encounter a long logon time after you enable the “Do not automatically make redirected folders available Internet Information Services (IIS) Installing and using certificates Windows SBS 2011 Standard Certificate may fail to install on a Vista or Windows 7 Client You receive a “The name of the security certificate is invalid or does not match the name of the site” warning when you try to connect Outlook 2007 to Small Business Server 2008 Not able to install Trusted certificate on SBS2008 How to Manually Install Certificates in SBS 2008 Request and install a trusted certificate Troubleshooting Certificate Mismatch Warnings in Outlook 2007 Clients on Small Business Server How Do I Distribute the SBS Self-Signed SSL Certificate to My Users? How to Obtain the Certificate Distribution Package in SBS 2011 Standard through Remote Web Access How do I import an existing trusted certificate? Remove a trusted certificate Managing Certificates The wizard that is used to add certificates no longer adds the FQDN of the server as a subject alternative name in the certificate request You receive a “The name of the security certificate is invalid or does not match the name of the site” warning when you try to connect Outlook 2007 to Small Business Server Cannot browse a local Web site Error 503 Service Unavailable when you browse Windows SBS websites How to Run a 32bit Web Application on SBS 2008/2011 Standard SBS 2011: Login to RWA fails with error 'The domain is null or empty' Getting to see the real IIS status codes from Internet Explorer SBS 2008-SBS2011/OWA, Remote fails with Http Error 500. Other Slow Connectivity for Outlook Anywhere and Sites that use the SBS Web Applications App Pool Reclaiming Disk Space Lost to IIS Logs on SBS Licensing Server Activation Windows activation fails and may generate error code 0x8004FE33 Windows is not genuine error in Windows 7 or Windows Server 2008 R2 Error 0xC004E002 during activation for Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista Error message when you try to activate Windows 7 or Windows Vista: “An error has occurred” Extending Your Activation Grace Period on Windows Server 2008 and 2008 R2 Client access licenses SBS 2011: Terminal Server/RDS Role Mail flow issues Cannot send or receive email How Do I Change Message Size Limits in SBS 2008/2011 Standard? How to Configure Trusted SMTP Relay in Exchange on SBS What to Check When Exchange Cannot Send Email to Certain Domains How to Send E-mails with Exchange Using a Different “From” Address How to Configure SBS 2011 Standard to Accept E-mail for Multiple Authoritative Domains Outlook Connectivity issues, Authentication or Certificate dialogs Slow Connectivity for Outlook Anywhere and Sites that use the SBS Web Applications App Pool You receive a “The name of the security certificate is invalid or does not match the name of the site” warning when you try to connect Outlook 2007 to Small Business Server 2008 Troubleshooting Certificate Mismatch Warnings in Outlook 2007 Clients on Small Business Server You receive a “The name of the security certificate is invalid or does not match the name of the site” warning when you try to connect Outlook 2007 to Small Business Server Certain Remote Client Access Can Break If You Change the Default Accepted Domain on SBS 2011 Standard Outlook Web Access (OWA) SBS 2008-SBS2011/OWA, Remote fails with Http Error 500. Error 500 Attempting to Access OWA on SBS 2011 Standard Your network is slow in Windows SBS 2011 Standard Unable to browse OWA,Error 1309 ASP.NET 2.0.50727.0 Error 500 Attempting to Access OWA on SBS 2011 Assign user permissions to access Office Outlook Web Access Database fails to mount Event ID 9519 “Error 0×80004005″ is logged in the Application log when you try to mount a database in Exchange Server 2010 or in Exchange Server 2007 Exchange mailbox store Exchange Services May Not Start Automatically After a Reboot How to Import and Export Mailboxes using PST Files in SBS 2011 Standard Move Exchange Server mailboxes and settings for Windows SBS 2011 Standard migration Other Unable to Open Exchange 2010 Management Console on Small Business Server 2011 Unable to open Exchange Management Console on Small Business Server 2011 Troubleshooting Exchange 2010 Management Tools startup issues Public Folders Empty 'CN=Servers' Container Causing Issues with Public Folders on Small Business Server 2011 Public Folder Replication Fails Due To Empty Legacy Administrative Group Mobile device synchronization with Exchange ActiveSync Error 500 while synchronizing mobile devices POP3 connector SBS 2008: Introducing the POP3 Connector Network and Web Connectivity Cannot browse companyweb An Administrators Quick Look at SharePoint for SBS 2011 Standard Repair user access to the internal website (SharePoint) Move the internal website for Windows SBS 2011 Standard migration Configure the Windows SBS 2011 Standard internal website (SharePoint) Move All SharePoint Foundation 2010 Databases for Windows SBS 2011 Standard to Another Server Recreate your SharePoint Foundation 2010 application and content database Error 503 Service Unavailable when you browse Windows SBS websites HTTP Error 503 Accessing Company Web on SBS 2011 Standard Another Reason Why Browsing CompanyWeb May Fail with HTTP Error 503 on SBS 2011 Standard Potential issues after installing SharePoint Foundation 2010 SP1 Dynamic Host Configuration Protocol (DHCP) client or server SBS Clients Lose Access to Shares and/or Cannot Get DHCP Addresses Reliability and Performance Server is slow or unresponsive Your network is slow in Windows SBS 2011 Standard Small Business Server 2011 starts slowly and many services do not start You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles Slow data transfer speed in Windows 7 or in Windows Server 2008 R2 Computer intermittently performs poorly or stops responding when the Storport driver is used in Windows Server 2008 R2 Troubleshooting “An unexpected error occurred” message when using Remote Web Access to connect to computers Errors that appear on a blue screen Update fixes an issue that causes Windows to crash 0xC0000005″ Stop error when the SVCHost.exe process that hosts Remote Desktop Services crashes in Windows Server 2008 R2 SP1 0x0000007F Stop error on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer 0×00000050 Stop error and an automatic restart on a Windows Server 2008 R2-based or Windows Server 2012-based computer 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL” Stop error on a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer 0x0000010c Stop error on a computer that is running Windows 7 or Windows Server 2008 R2 0x0000008E Stop error on a computer that is running Windows 7 or Windows Server 2008 R2 Server stops responding (hangs) Your network is slow in Windows SBS 2011 Standard Small Business Server 2011 starts slowly and many services do not start You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles Slow data transfer speed in Windows 7 or in Windows Server 2008 R2 Computer intermittently performs poorly or stops responding when the Storport driver is used in Windows Server 2008 R2 Troubleshooting “An unexpected error occurred” message when using Remote Web Access to connect to computers Small Business Server (SBS) Components Backup Windows Server Backup May Fail Because of the SQL VSS Writer Windows Server Backup May fail the Exchange Consistency Check How to back up Small Business Server 2011 System State Backups and SBS 2008 Repair Windows Server Backup Companyweb (Intranet) Error 503 Service Unavailable when you browse Windows SBS websites HTTP Error 503 Accessing Company Web on SBS 2011 Standard Another Reason Why Browsing CompanyWeb May Fail with HTTP Error 503 on SBS 2011 Standard Potential issues after installing SharePoint Foundation 2010 SP1 Update Services WSUS 3.0 Self-update is not working on Windows Small Business Server and Event ID 13042 is generated Unable to connect to WSUS Administration Website Known Issues after Installing WSUS Update KB2720211 Further Hardening of WSUS Now Available How to Move WSUS Content and Database Files to a Different Volume How to Manually Create the Windows Small Business Server 2011 Standard and WSUS Group Policies Objects Repair Windows Server Update Services Remote Web Workplace or Remote Web Access You get HTTP Error 401.2 – Unauthorized when you browse RWA on Windows Small Business Server SBS 2011: Login to RWA fails with error 'The domain is null or empty' SBS 2011: Home Page of RWA display an error “There is a problem with this Web page” SBS2011: Unable to login to RWA – An error (87) occurred while enumerating the groups. The group's SID could not be resolved Clipboard redirection does not work from within Remote Web Access in SBS 2011 Users fail to log into RWW with Password error Server Management Console SBS Console Home tab shows Updates status as “Not Available” Windows SBS Console may crash SBS 2011 Console Crashes when you click on Shared Folders and Web Sites Tab SBS console crashes when duplicate entries from AV products are written into Security Center SBS Monitoring and Reporting Managing Event Alerts in Your Reports – An SBS Monitoring Feature Enhancement How to Recreate the SBSMonitoring Database Repair Monitoring and Reporting Features in Windows Small Business Server 2011 Standard Move Data Wizards Managing Server Storage Microsoft SQL Server Issues with SQL Server 2008 R2 for Small Business Requirements for Installing SQL 2008 Standard Edition for Small Business SQL Server 2008 R2 setup failing on Windows 2008 R2 SBS How to diagnose “Operating system supported for edition” pre-requisite errors while installing SQL 2008 Standard Edition for Small Business Where is my SQL Server 2008 R2 for Small Business Product Key? Upgrading the Companyweb database to SQL Server How to Migrate Companyweb to a SQL 2008 R2 Standard Instance on SBS 2011 – Part 1 How to Migrate Companyweb to a SQL 2008 R2 Standard Instance on SBS 2011 – Part 2: Premium Second Server How to Migrate Companyweb to a SQL 2008 R2 Standard Instance on SBS 2011 – Part 3: Migrating the Content Database Configuring or troubleshooting SQL Server after it is installed General Network error, “Communication link failure,” or “A transport-level error” message when an application connects to SQL Server Installation and Migration Installation issues You May Get an Error “Verify that the Source Server Name is Correct” While Trying to Install SBS into an Existing Domain A migration installation of SBS 2011 Standard May Stop With The Message The Source Server Does Not Meet Minimum Requirements For Migration Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller The SBS 2008 or 2011 Standard Migration Wizard may fail to launch due to an incomplete setup Exchange Server 2010 is in evaluation mode after installation or repair in SBS 2011 Standard How to Clean Up Active Directory after an Unsuccessful Migration Migrating SBS to a new server or to new servers SBS 2011 Standard Migrations – Keys to Success SBS 2011 Standard Migrations – Keys to Success – Part 2: The Setup Phase SBS 2011 Standard Migration – Keys to Success – Part 3: Post Setup and Common Failures Install Windows SBS 2011 Standard in migration mode Introducing the SBS 2011 Migration Preparation Tool Providing an Answer File in SBS 2011 How to Determine the Number of Days Left for SBS 2011 Standard Migration Other Catalog of Windows Small Business Server 2011 Standard Error Messages SBS 2011 Standard Migrations – Keys to Success SBS 2011 Standard Migrations – Keys to Success – Part 2: The Setup Phase SBS 2011 Standard Migration – Keys to Success – Part 3: Post Setup and Common Failures Problems with a task in the Guided configuration and migration tasks Update 2 for the Windows Small Business Server 2011 Standard Migration Preparation Tool SBS 2011 Standard Edition Source Tool Scan Fails Unable to run the migration preparation tool on SBS server Move the internal website for Windows SBS 2011 Standard migration Move settings and data to the Destination Server for Windows SBS 2011 Standard migration Move users' shared data for Windows SBS 2011 Standard migration Virtualization Virtualizing Small Business Server You Cannot Install the Hyper-V Role on the SBS 2008 Primary Server  

Deploying Windows Server 2012 R2 Standard/Datacenter with Windows Server Essentials Experience role in an Existing Active Directory Environment

[This post comes to us courtesy of Sandeep Biswas and Rituraj Choudhary from Microsoft Global Business Support] In this post we will discuss deploying Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter with Windows Server Essentials Experience role in an existing Active Directory environment. There are certain facts that we must be cognizant of in this scenario: The Windows Server Essentials Experience role can only be deployed in a domain environment. If you intend to install Windows Server Experience role on a Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter edition in an environment with a pre-existing Active Directory domain, it does not have to be a domain controller. However, if an Active Directory domain does not exist, installing the Windows Server Essentials Experience role on a Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter edition will create an Active Directory domain, and the server will become the domain controller at the root of the forest and domain, holding all the FSMO roles. The Windows Server Essentials Experience role can only be deployed into a single domain. Also, a read-only domain controller cannot exist in this domain. These limitations stand out irrespective of the Windows Server editions that we can deploy Windows Server Essentials Experience role on. In order to deploy a Windows Server 2012 R2 Standard or Windows Server 2012 R2 Datacenter in an existing domain, first, complete the initial setup. Once the installation is complete and the server reboots to the desktop, log on with the local administrator account. Make sure you are connected to the local network. To do so, you may ping the internal domain name to verify that it resolves to the IP address of the source server. The next step is to add this server to the domain using native methods. To do so, launch the System Properties . Click Change on the Computer Name tab. If you wish to change the Computer name, type a new name. Click the radio button Domain and type the existing domain name and then click OK . On the next screen, enter the domain administrator credentials to join the existing domain and proceed by clicking OK button. After the server is successfully joined to the domain, you will be notified with a welcome message. Once you acknowledge the message by clicking OK , you will receive a prompt to restart the server. Save your work, close any open files, and then restart the server. At the subsequent logon prompt, click the Switch user icon and then click Other user . Log on to the server with the domain administrator credentials. Once logged on to the desktop, the Server Manager page will pop up. Click Manage and then click Add Roles and Features . This will pop up the Add Roles and Features Wizard . Follow through by clicking Next on each of these pages: Before you begin , Select installation type , and Select destination server . On the Select server roles page, click to select the Windows Server Essentials Experience role and then click Next . You will receive a popup to add features required for Windows Server Essentials Experience role. Click Add Features to proceed. Proceed by clicking Next button on the remaining pages of the wizard. On the Confirm installation selections page, click Install . You will receive a notification after the installation completes as follows. Click Close to close this wizard. Back on the Server Manager console, you will now receive a notification flag with a yellow exclamation mark. Click the notification flag and then click Configure Windows Server Essentials . The above action will launch the Configure Windows Server Essentials wizard. Click Configure button to configure Windows Server Essentials. Wait for the configuration to complete. Click Close when it is done. You are now ready to use your Windows Server 2012 R2 with Windows Server Essentials Experience role configured as a member server in your existing domain. You may now proceed to configure Essentials features based on your needs through the Windows Server Essentials Dashboard. In our next migration series post we will discuss how to add a Windows Server 2012 R2 Essentials in an existing Active Directory. Stay tuned!

Server folders on another server

[Today’s post comes to us courtesy of Yang Cao from the Windows Server Essentials product team] For midsize businesses, having more than one server becomes necessary. Even for small businesses, it is common to have more than one server. One of the servers might be the domain controller, another might be running a line of business application; maybe there is a server hosted in the public cloud, while another file server might be sitting on-premises for faster file access. In situations like these, the data might be stored on multiple servers, and the end user needs to access the data with different Server Message Blog (SMB) path forms, for example, \server1folder1 and \server2folder2 . This becomes a burden for the end user to remember which file is on which server; it is also inconvenient for the administrator if he or she needs to move data from one server to another without confusing the end user or breaking existing applications. In Windows Server 2012 R2 Essentials and Windows Server 2012 R2 with the Windows Server Essentials Experience role enabled, it is possible to create and manage a server folder on a second server within the same network, and to allow the end user to access the share with one SMB path form, for example, \ContosoShared Foldersfolder1 or \ContosoShared Foldersfolder2 . Creating a server folder on a second server is easy. You start with the Add a folder task on the STORAGE page. The Add a Folder Wizard opens: Fill in the name of the server folder, and then click Browse . If there are other servers in the same domain, those servers will be found and listed in the tree view. You could expand the node and find the folder that you want to share. If the folder doesn’t exist yet, click Create New Folder to create the folder at the desired location first. Follow the guidance and finish the wizard. On the last page of the wizard, you will notice the sharing path of the new server; although it is physically located on a second server, the path starts with the name of the primary server running Windows Server Essentials. From the administrator’s perspective, the new folder’s location is on a different server, and he or she can continue managing all the server folders by using the Dashboard. From an end user’s perspective, when she opens the Shared Folders shortcut from the desktop of a client computer, she sees all the shared folders, and she doesn’t need to know that the HRFolder is actually on another server. We hope you find this feature useful. As always, please get started by downloading the trial today and joining the conversation on our forum .

Data Protection in Small and Midsize Businesses Solution Guide Published

[This post comes to you courtesy of Kumud Dwivedi from Content Publishing] If you are a small to midsize business that is looking for a reliable way to protect business data, Windows Server 2012 R2 Essentials and Windows Server 2012 R2 provide a solution to protect your data by centralizing data storage, restricting access to data, and backing up data on-premises and in the cloud. If your business has up to 25 users and 50 devices, use Windows Server 2012 R2 Essentials. For up to 100 users and 200 devices, use the Standard or Datacenter editions of Windows Server 2012 R2 with the Windows Server Essentials Experience role installed. To learn more about how to use Windows Server 2012 R2 Essentials and Windows Server Essentials Experience, see Data protection in small and midsize businesses .