This is the archive for older Windows 7, 8, Server 2012, 2008, 2003, R2 information that was previously on TechNet.
Category Archives: SBS 2011
Meltdown and Spectre
Happy New Year … Not!
With the New Year comes a new class of malicious attack that can impact IT systems. This time, the attack is hardware based, affecting mostly Intel based systems, and to some extent, AMD systems as well.
Here is a list of resources that highlight what it is all about and how to mitigate against this new threat. In the words of Microsoft, “Don’t panic.”
- What is Meltdown and Spectre? https://meltdownattack.com/
- Summary paper and Mitigation Steps for Organisations
https://www.docdroid.net/3Dw8WFD/meltdown-and-spectre-mitigation-for-organisations.pdf - Updated AntiVirus vendor compatibility chart
https://docs.google.com/spreadsheets/d/184wcDt9I9TUNFFbsAVLpzAtckQxYiuirADzf3cL42FQ/htmlview?usp=sharing&sle=true - Summary of Microsoft information in one place
http://www.essential.exchange/2018/01/04/windows-speculative-execution-client-server-patches-mitigations-detection-summary/ - GRC InSpectre. Test and enable protection against Spectre and Meltdown. https://www.grc.com/inspectre.htm
Office 365 migrations
I just spent the weekend working performing some SBS to Office 365 migrations.
Here are some useful links that make the process a whole lot easier.
Export mailboxes to PST for Exchange 2010 (SBS 2011 Standard)
Export mailboxes to PST for Exchange 2007 (SBS 2008)
Import PST files to Office 365
- https://technet.microsoft.com/en-us/library/ms.o365.cc.ingestionhelp.aspx
- The above link neglected to mention that the Mailbox Import Export Role must be assigned to the account that is performing the migrations – http://www.alexandreviot.net/2016/01/12/office-365-import-export-role/
Enabling Autodiscover for Outlook in SBS Exchange Environments
- For SBS 2008 – http://www.mcbsys.com/blog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
- For SBS 2011 – http://kirb.it/enable-office-365-auto-discover-for-outlook-in-sbs-2011-exchange-environments/
Getting Outlook 2007 and Outlook 2010 to work with Office 365
- The following link lists the minimum requirements needed to quickly get your Outlook desktop client running with Office 365.
- http://www.netdummy.net/office365-client-updates.html
- With SBS 2011, it is necessary to remove the Service Connection Point (SCP)
- Show SCP information: Get-ClientAccessServer | Select Name, AutoDiscoverServiceInternalUri
- Remove SCP information: Set-ClientAccessServer -Identity “[Servername]” -AutoDiscoverServiceInternalUri $NULL
Importing LegacyDN information
Problems connecting Outlook to Office 365
- Microsoft’s Outlook Support Center Wizard – https://diagnostics.office.com/#/?env=Maven (
AND if you happen to still be using SBS 2003 (I certainly hope not!), you can use Exmerge or Outlook to output individual mailboxes to PST. Do it soon!
Windows 10 support on Windows Server Essentials and Small Business Server
The Essentials Server team have released a blog post to highlight which client versions are supported on currently supported Windows Server Essentials and Small Business Server 2011. The blog post can be read here – http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx
Basically, if you need to connect a Windows 10 client to Windows Server Essentials 2012 R2, which is probably the most common scenario, you will need to perform a manual client connector installation. A fix for the server is scheduled to be released on 17 November 2015.
Another common scenario would be the joining of the client connector for a Windows 10 client to Small Business Server 2011. In this case, 2 lines need to be added to the XML file on the server, which is located at C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml. Add the following 2 lines.
<OS Architecture="9" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, AMD64" id="9"/> <OS Architecture="0" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, x86" id="10"/>
Exchange TLS & SSL Best Practices
For those using Exchange on-premises (including SBS 2011), here are some best practice recommendations from the Exchange Team.
http://blogs.technet.com/b/exchange/archive/2015/07/27/exchange-tls-amp-ssl-best-practices.aspx
In a nutshell,
- Deploy supported operating systems, clients, browsers, and exchange versions
- Test everything by disabling SSL 3.0 on Internet Explorer
- Disable support for SSL 3.0 on the client
- Disable support for SSL 3.0 on the server
- Prioritize TLS 1.2 ciphers, and AES/3DES above others
- Strongly consider disabling RC4 ciphers
- Do NOT use MD5/MD2 certificate hashing anywhere in the chain
- Use RSA-2048 when creating new certificate keys
- When renewing or creating new requests, request SHA 256-bit or better
- Know what your version of Exchange supports
- Use tools to test and verify
- Do NOT get confused by explicit TLS vs. implicit TLS
- (For now) Wait to disable TLS 1.0 on the Exchange server
Windows 7, 8.1, 10, SBS and Essentials Client Conntector – What works, and what doesn’t
The Essentials Server team have just published a blog post which gives you an at-a-glance look at what features are supported and not supported with the six current (and recently past) SBS and Essentials SKUs.
Read the blog post here – http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx
Top Support Solutions for Windows Small Business Server 2011 Standard
Pointer to the SBS Team blog on the top issues faced and corresponding resolutions for SBS 2011. This is a useful reference – http://blogs.technet.com/b/sbs/archive/2014/02/18/top-support-solutions-for-windows-small-business-server-2011-standard.aspx
The links are repeated here in case the page disappears.
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
-
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
-
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
-
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
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.
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
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
-
Exchange mailbox store
-
Other
-
Public Folders
-
Mobile device synchronization with Exchange ActiveSync
-
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
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
- 0x00000050 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
-
Companyweb (Intranet)
-
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 Monitoring and Reporting
-
Move Data Wizards
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
-
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
Migrating Email from SBS Exchange to Office 365
In the past few months, I have been working with some clients on moving their existing Small Business Server (SBS) systems over to the Microsoft cloud based Office 365 email system. There are a number of issues and possible gotchas in making this transition which will be discussed here. Note that this blog post is targeted to the small business community with existing SBS 2003, SBS 2008 or SBS 2011 deployments that are looking to move their email services to Office 365, while maintaining their existing network. We will not be considering Office365 migration method in this move as the costs and complexity of implementing this in a small business are prohibitive.
The pre-requisite when performing such a migration, is to plan and work out a migration path for email services. Questions to be considered are:
- Do we need to migrate all the old email data, or should some be archived?
- Are there old accounts that can be decommissioned?
- What distribution groups and contacts need to be migrated across?
- Are there any Send As and Send on Behalf of permissions that need to be addressed?
- Are there individual permissions on Calendars and Folders that need to be recreated?
- How will we move the old email data from Exchange on premises to Office 365?
Moving Email data from On-premises Exchange to Office 365
Central to the entire issue is retaining old emails and settings. There are a number of ways to move the data across to Office365.
- Export-Import. This method involves exporting the current emails to PST and re-importing them into Office 365 once Outlook has been configured.
- Migrationwiz.com is a fast and easy way to move mailboxes at a low cost.
- Office365 Migration wizard. This is a built in tool from Microsoft to help in performing a migration from on-premises Exchange. It requires an Azure subscription and the installation of the Directory Sync tool and has some tough pre-requisites for SMBs. The process is detailed on technet here – http://technet.microsoft.com/en-us/library/jj573653.aspx
One main drawback from using any method that does not synchronize the Office 365 platform to your existing Active Directory is dealing with the issue of Auto-Complete or Suggested Contacts. After the migration, it is quite likely that replies on old emails or emails sent using the stored contact information in Auto-Complete or Suggested Contacts will result in a Undeliverable error as follows:
IMCEAEX-_O=MyDomain_OU=First+20Administrative+20Group_cn=Recipients_cn=bOldLastName@domain.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Create Users and Set up Domain in Office 365
In this step, you need to set up and recreate all the users, distribution groups, and domains to match what you have on-premises. In the public DNS, set the MX records to point to your on-premises Exchange until you are ready to receive emails at the Office 365 service. Ensure that the Autodiscover and other DNS services are set up properly.
Setting up the Outlook Profile
One of the main issues with setting up Outlook for Office 365 on an existing SBS domain is the existing autodiscover configuration set up for each user account. The following steps should be followed to ensure a simple, incident free set up of Outlook on Office 365.
- Log in to the PC as the user. The configuration is done per user.
- Update your PC with a the latest patches, especially Microsoft Office patches and Service Packs.
- Log in to the Office 365 portal using the users email address and assigned password.
-
Install software and connect it to Office 365
-
You will need to sign in to Office 365 again using the user’s credentials.
-
The Office 365 setup application will note that manual steps will be required (which involves setting up the Outlook profile as detailed here).
-
Once the set-up is completed, you will need to create 6 new registry entries. (thanks to https://gothamweb.com/esupport/index.php?/Knowledgebase/Article/View/133/26/outlook-2007-connecting-to-a-local-exchange-server-instead-of-hosted-exchange)
For Office 2007, the registry key is [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover]
For Office 2010, the registry key is [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover]
The six entries are all DWORD. (NOTE: all but one entry are set to 1)
“PreferLocalXML”=dword:00000001
“ExcludeHttpRedirect”=dword:00000000
“ExcludeHttpsAutoDiscoverDomain”=dword:00000001
“ExcludeHttpsRootDomain”=dword:00000001
“ExcludeScpLookup”=dword:00000001
“ExcludeSrvRecord”=dword:00000001
They should be displayed among other entries like this.
-
Download and run the two AgileIT tools from http://www.agileit.com/news/office-365-autodiscover-xml-tool-released/. Just enter the domain name and click OK.
-
Now you can Add a new Outlook Profile from Control Panel-Mail (32-bit). You will see the existing Outlook Profile there, which can be kept as a backup, as you may need it later for export to PST purposes.
-
The local autodiscover settings that have been configured earlier will kick in and set up the account. You will need to log in using the Office 365 credentials.
You can also add the on-premises Exchange profile to this new profile, if you are planning to export the old email data or manually transfer information over to the office 365 account.
With smaller sites, this is a quick and easy way to manage your Office 365 migration. With larger installations, the Office 365 migration wizard using Azure and Directory Sync may be a more efficient method. In the end, it is up to the business owner, with advice from the IT consultant, to work out which method is preferred.
UPDATE: There is a really good article on how to use Azure Active Directory to handle password sync between your local AD and the new Office 365 AD – www.infostream.cc/dirsync-aadsync
Http://Connect shows a 404 – File or directory not found error page
Http://connect is used in Small Business Server and Windows Server Essentials to configure and join client computers to the domain. There is a known issue with Trend Micro’s Worry Free Business Security suite version 7 and 8 which causes this issue.
The solution is to disable (NOT DELETE) the CGI-exe and ISAPI-dll modules on the SBS Client Deployment Applications Website in IIS.
-
To do this, you need to start up the Internet Information Services (IIS) Manager. Note: There are 2 of these located in Administrative tools. Select the non-numbered (version 7) one.
-
Expand to the SBS Client Deployment Applications Home and locate Handler Mappings.
-
Double-Click Handler Mappings. Then locate CGI-exe. Right-Click and Edit Feature Permissisons.
-
Remove the tick on Execute. You will now see CGI-exe and ISAPI-dll listed in the disabled section. Click OK.
-
Return to the SBS Client Deployment Applications Home, right-click on the website, select Manage Web Site, and restart the site.
Error: Cannot connect the computer to the server because either another software installation is in progress, or, the computer has a restart pending.
I have been seeing quite a number of systems coming up with this error message when attempting to install the Client Connector Software for SBS 2011 Essentials.
“Error: Cannot connect the computer to the server because either another software installation is in progress, or, the computer has a restart pending. Either complete the installation process, or, restart the computer and try to connect again.”
The first thing to do is obvious – Reboot the computer. But then again, there would not be anything to blog if it were that easy. Obviously, that has been attempted and the error remains. Apparently, this is often caused by programs not cleaning up their installation settings.
The fix is fairly simple, if you can remember where the registry setting is.
Open up Regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager. Rename the key named PendingFileRenameOperation to something else.
That should resolve the issue.