First published on TECHNET on Oct 15, 2013
Hi All, my list is Bill and I work in the Windows Server – File Services group. One of my main responsibilities is to enhance the Server Manager user interface. We have barely delivered Work Folders as part of the Windows Server 2012 R2 turn. I have been following the forum and there have been several questions about Work Folders and port conflicts with other IIS Websites. For this reason I posted this web log for steering .
Covered in this article :
- Diagnosing Port Conflict between Work Folders and Windows Server Essentials or other web applications.
- Changing Port Configuration in Work Folders
- In-Place Upgrade from Windows Server Essentials to Windows Server Standard
- Guidance for Using Hyper-V for Current Enabling of Work Folders and Windows Server Essentials using their default configuration
- PROBLEM STATEMENT
- DIAGNOSING WORK FOLDERS AND WINDOWS ESSENTIALS PORT CONFLICTS
- CHANGING WORK FOLDERS CONFIGURATION
- NO CONFIGURATION FOR BOTH FEATURES
Using any web application with Work Folders may create port conflicts between the web application and Work Folders. work Folders uses by default ports HTTPS=443 and HTTP=80. Most web applications use the like well known ports. In the specific lawsuit of Windows Server Essentials and Work Folders, both features use the lapp nonpayment ports. The first feature to initialize the ports will entirely own them. This creates a port conflict for one of the features, depending on startup and how the features where configured.
work Folders is available in Windows Server 2012 R2 Essentials as part of the File and Storage Services character. work Folders uses the IIS Hostable Web Core feature and all management is performed via the Work Folders canvas in Server Manager arsenic well as via Windows PowerShell cmdlets. Windows Server Essentials is managed via its dashboard and the IIS Management UX. Both products assume exclusive entree of the SSL port ( 443 ) and HTTP port ( 80 ). This is the default option configuration for both products .
The administrator has the ability to change both feature configurations when both products are enabled. Changing the port conflicts allows for both products to be installed on Windows Server 2012 R2 Essentials. If the administrator does not want to change the default ports, they have the choice of enabling either Windows Server Essentials feature or work Folders. This is at their discretion based on business necessitate .
If the administrator would like to change the ports on either feature, they need to open the firewall on the server for the particular ports they defined for the feature. This can be accomplished by navigating to Control Panel and modifying the Windows Firewall configuration. further solve is necessary in collaboration with a network administrator to configure the routers vitamin a well. This text file will not cover network configuration .
See : hypertext transfer protocol : //msdn.microsoft.com/en-us/library/bb909657 ( v=vs.90 ) .aspx
DIAGNOSING WORK FOLDERS AND WINDOWS SERVER ESSENTIALS PORT CONFLICTS
In the consequence where both features are enabled on the same waiter with default port shape the behavior may be elusive and only one feature will work. In the casing of Windows Server 2012 R2 Essentials, Windows Server Essentials is enabled out of the box. This means the ports will have been configured and ownership will be IIS. When you enable work Folders, the initiation will succeed and Server Manager may not be able to manage the work Folders feature on the Windows Server Essentials waiter. If the administrator navigates to the SERVICES elementary tile they will see the following :
The Sync Share Service will not start if both ports defined in its configuration are being used by another serve. This will be a clear indication the default ports are not available to Work Folders. If on the off prospect one of the ports is available the Sync Share Service will become operational. There will be no indication there is an mistake .
Please eminence if port 443 is used by another process, although Work Folders Service will start and be operational, any SSL traffic will not be directed to Work Folders. SSL=443 is the nonpayment batten interface used by Work Folders. The administrator would have to look at the port definition in the file vitamin c : \windows\system32\SyncShareSvc.config and compare the configuration of websites defined in the IIS UX. Once they check the port information in IIS they can assess the conflict .
Using Event Viewer to view SyncShareSvc errors
In the case both ports are not available the follow error can be found in the arrangement event log .
Using Event Viewer ( eventvwr.msc ) navigate to the Windows Logs, System Channel. The error should be from the Service Control Manager. The error returned will be in the system channel in the form : “ The Sync Share Service terminated with the following service-specific error : Can not create a file when a file already exists ” This is the generic message when both ports are not available .
Using IIS PowerShell cmdlets “Get-WebBinding” to list port bindings
Get-WebBinding is a handy control for showing IIS web site port bindings on your server. In this particular case we want to see all the IIS web site bindings active on your server .
ß command on left field will give you the following output :
model 1 – both ports in function by IIS web site :
The study Folders SyncShareSvc will not start because both default ports are being used by IIS .
example 2 – one port used by IIS web site – SSL PORT :
As mentioned in the previous section, if Work Folders has access to one port the service SyncShareSvc will come up. work Folders uses larboard 443 as the default. In example 2 Work Folders service would start and look functional. The output of Get-WebBinding would show the administrator workplace Folders would not function as defined in the default configuration .
If neither port is in use by another web application, the list above would be empty .
CHANGING WORK FOLDERS CONFIGURATION
On the Server Manager Service Primary Tile locate the SERVICES tile. Locate the SyncShareSvc. Verify it is stopped. If it is not stopped, select the SyncShareSvc and stop it.
navigate to the directory on the server where work folders feature is enabled .
> compact disk c : \windows\system32
Edit the file with your front-runner editor ( file name = SyncShareSvc.config )
Locate the segment below and make the changes to your port designation
exemplar you want to change SSL Port from 443 to 12345. Change the port number and close the file. Because the synchronize service does not run under the system designation it does not have the privileges to access different ports other than the default option. It runs under LOCAL SERVICE. Because of this designation the administrator has to run another command. In an exalted command windowpane type the follow dominate :
Netsh http add urlacl url=https://*:12345/ user=”NT Authority\LOCAL SERVICE”
voyage to SERVICES tile in Server Manager and start the military service SyncShareSvc .
Since the Work Folders configuration on the node defaults to either HTTPS=443 or HTTP=80 there is extra configuration to override the default option ports. The administrator will need to change the URL for connecting to the Windows Server hosting the clients synchronize contribution. normally all that would be necessary is the URL of the server. Since the port has changed there is an extra parameter in the URL which is – colon port number “ : # ”. This number matches the configuration in the shape file on the server SyncShareSvc.config. See example of the personal computer node shape below :
note : When the administrator changes the nonpayment ports for exploit Folders they can not use the car discovery process. They can communicate the new URL using Group Policy or a standard electronic mail communication with the URL and modern port definition .
IIS References for Configuration Changes
For Windows Server Essentials port configuration see the Windows Server Essentials software documentation using the IIS management UX .
hypertext transfer protocol : //www.iis.net/configreference/system.applicationhost/sites/site/bindings/binding
NO CONFIGURATION CHANGES FOR BOTH FEATURES
The administrator has another option for running both Windows Server Essentials and Work Folders on the same server. There are posts on-line which already recommend an in-place license upgrade from Windows Server Essentials to Windows Server Standard. This has a twofold improvement. It allows for greater usage of Windows Server Essentials and has a license for two Hyper-V machines. The administrator would then disable Windows Server Essentials in the main master of ceremonies and user the two Hyper-V machines one for each feature. Windows Server Essentials in one VM and Work Folders in the other. They can both use their default configurations and knead concurrently on the single host .
You can upgrade in topographic point from Windows Server 2012 R2 Essentials to Windows Server Standard. — – Windows Server Standard is the only in-place upgrade. You can not use the command below to upgrade to Windows Server Storage, Windows Server Datacenter etc. The command for upgrading from Windows Server 2012 R2 Essentials to Windows Server 2012 R2 Standard is :
dism /online /set-edition : ServerStandard /accepteula /productkey :
Read more: Download XAMPP for Windows – Free – 8.1.0
From < windows2012 essentials upgrade to windows 2012 server standarddataenterprise >
There are several ways to configure Work Folders in an environment which already has established web applications. You have the ability to change the ports of either application. In the shell of an IIS application you can use the existing IIS UX. In the font of WorkFolders you can follow this guide. The administrator besides has the ability to run Work Folders in a separate VM which has the benefit of leaving their stream shape as is and install work Folders with default option settings .