Share the post "Unable to access Folder Redirection share"
A user on a Windows 7 client was unable to access the Folder Redirection share on a Windows Server 2012 Essentials server. Oddly the user could access other shares on the server without issue and they could access the Folder Redirection share from another computer.
In diagnosing the issue I added an additional share to the Folder Redirection folder and discovered the user was able to access that folder.
That led me on a bit of a goose chase until I eventually discovered the user could access the share by using the IP address or FQDN. For example \\192.168.0.1\folder redirection or \\server.domain.local\folder redirection.
The solution was to clear/re-initialise the offline files cache on the Windows 7 computer as per http://support.microsoft.com/kb/942974
To resolve this problem, re-initialize the cache of offline files. To do this, follow these steps:
- Click Start, type regedit in the Start Search box, and then press Enter.Note If you are prompted for an administrator password or for confirmation, type the password or click Continue.
- Locate the following registry subkey, and then right-click it:
- Point to New, and then click Key.
- Type Parameters in the box.
- Right-click Parameters, point to New, and then click DWORD (32-bit)Value.
- Type FormatDatabase, and then press Enter.
- Right-click FormatDatabase, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor, and then restart the computer.
Note Make sure that files are synchronized before you add this registry entry. Otherwise, unsynchronized changes will be lost.
Share the post "SBS 2008 updating rebooting loop"
SBS 2008 on restarting after Windows updates were installed would show Applying computer settings followed by Applying update 3 of 3. It would then show a black screen with a flashing cursor in the top left of the screen.
After some time the server would restart and the process would repeat in an endless loop.
To resolve the issue perform the following steps:-
- Boot from the SBS installation CD.
- When prompted select the Install Language and click Next.
- Instead of continuing the installation select the option to Repair windows.
- Select the option to open a cmd prompt.
- Enter the following command:-
- ren c:\windows\winsxs\pending.xml pendingold.xml
- Close the cmd prompt and select the option to restart.
The server should now start and allow you to logon. You’ll now need to determine which update/s caused the issue to ensure it doesn’t happen again.
Share the post "SBS 2008 loses network gateway IP address after reboot"
A server running SBS 2008 lost remote network connectivity after being updated with IBM’s Update Express System Pack. Upon investigation the cause was found to be that the gateway that was missing from the network settings.
The gateway was re-entered but after a reboot the gateway was missing again.
A quick search revealed that the Gateway key in HKLM/System/CurrentControlSet/Services/Tcpip/Parameters/Interfaces for the interface in use had a blank line on the first line with the gateway IP address listed on the second line.
Removing the blank line resolved the issue and the gateway remained after rebooting the server.
It is then necessary to apply this hotfix to prevent the issue from happening again.
Share the post "Outlook 2013 display issues"
Recently we’ve seen an issue with Outlook 2013 where display corruption occurs. Some of the issues include:-
- The folder list blurs/corrupts visually when scrolling through it.
- Menu’s in open emails lose their formatting.
In order to resolve the issue the first thing to try is updating the video card drivers.
If that doesn’t fix the issue you’ll need to disable hardware acceleration for Office applications:-
- Start any Office 2013 program.
- On the File tab, click Options.
- In the Options dialog box, click Advanced.
- In the list of available options, click to select the Disable hardware graphics acceleration check box.
- Click Ok.
More information can be found in KB 2768648.
Share the post "Windows Server 2012 R2 Hyper-V guests lose network connectivity"
On a HP Proliant ML310e Gen8 V2 server was installed Windows Server 2012 R2 Standard edition. The Hyper-V role was enabled and two guest VM’s were installed. One was Windows Server 2012 R2 Standard Edition and the other was Windows Server 2008 R2.
Periodically both VM’s would lose network connectivity. No error showed in the event logs of the Host during this time. Attempting to ping any network address from the VM failed as did attempting to ping the IP addresses of the VM’s. During this time the other physical NIC on the host that wasn’t part of the Virtual switch continued to operate and respond as expected.
Disabling and Enabling the NIC on the Host temporarily resolved the issue as did physically removing and reinserting the network cable into the physical NIC on the Host.
The network card on the host server is a Broadcom and was using driver version 22.214.171.124.
There have been issues with Virtual Machine Queuing and Broadcom NIC’s in the past and it would appear that this is still the case on Gen8 HP hardware, at least in this case.
To resolve the issue disable Virtual Machine Queuing (VMQ) on the host for the problematic NIC.
- On the host open device manager.
- Expand Network Adaptors
- Right click on the Network Adaptor that is part of the Hyper-V Virtual switch and select Properties.
- Select the Advanced tab.
- Under “Property” select Virtual Machine Queue
- Set the value to “Disable” and click on OK.
- Reboot the host.
Share the post "Apple iOS devices – RD Client with Remote Desktop Gateway support"
If you have an Apple device (iOS) and use it to connect to Windows devices via Remote desktop you can now download an official Microsoft app from iTunes (and it supports Remote Desktop Gateway)
Share the post "How to download and then install Office 365 Professional Plus"
One of the benefits of some of the Office 365 plans is that they include Office 365 Professional Plus. This can be installed by logging into the Office 365 portal and selecting to install the software. This starts a streaming installation.
Whilst this is ok for a single install it is very time and bandwidth consuming for multiple installs.
Because of this, Microsoft have provided the ability to download all the installation streaming bits so that multiple installs can be performed without the need to download the bits each time.
You can also download the bits without an Office 365 subscription. You do however need a subscription (or a product key) to activate the installation.
Step by step to download Office 365 Professional Plus
- Create a folder on the computer that you wish to have the bits downloaded to. For the example we will create a folder called office365pro. Then create a share for that folder. For the example we are using the same name as the folder for the share, office365pro. This may be on a server that the clients (that will have Office 365 Pro Plus installed) have access to.
- Take note of the share path. Example:- \\servername\office365pro
- Download the Office Deployment Tool for Click-to-Run
- Run officedeploymenttool.exe and select where to extract the files.
- Once extracted you will have two files. Setup.exe and configuration.xml
- Open the configuration.xml file in notepad.
- Modify the Sourcepath to match the path you noted in step 2.
- If you don’t want Visio, remove the Visio section.
- Remove the <!– from the very first configuration line. This uncomments the line so that it now looks like this:-
- <Add SourcePath=”\\servername\office365pro\Office\” OfficeClientEdition=”32″ >
- Note the other sections in the file that can be uncommented to perform silent installs, specify logging, enable updates and set activation. For detailed information refer to the Reference for Click-to-Run configuration.xml file.
- I’ve created a preconfigured configuration.xml –> configuration It is configured to download the 32bit version of Office 365 Pro Plus but not Visio Pro. The other options are left commented out except for logging. All you will need to modify is \\Server\Share to \\yourservername\yourshare
- In order to proceed to the next step you must be using a system that meets the Office 365 system requirements. So if necessary copy setup.exe and your modified configuration.xml to a system that meets the requirements. If you attempt to do the next step on any other system (for example, Windows XP, SBS 2008, Server 2008 etc) you will receive the error setup.exe is not a valid Win32 application.
- Open an elevated cmd prompt on a system that meets the requirements and change to the directory that contains the setup.exe and configuration.xml files.
- Enter this command setup.exe /download configuration.xml
- This will now download the installation bits to the share specified. Note: You must have permission etc to the share where you are attempting to download the bits to.
- This process will take some time depending on your internet speed. All bits will be downloaded into a folder called office within the share. The path will be \\servername\office365pro\office\office which will contain a Data folder and other files.
- This process can be troublesome and not successfully download all of the required files. We will verify that in the next section, installing.
- Once the download is complete, place the setup.exe and configuration.xml into \\servername\office365pro\office This is so we can run the setup.exe from the share when installing in the next section.
Installing Office 365 Professional Plus from a downloaded source.
This section describes how to manually install Office 365 Pro Plus. The cmd in Step 4 below can be used to automate the installation via script, Group Policy, SCCM etc. For an automated install you will need to modify the configuration.xml to suit your requirements.
- On the client/computer that you wish to install Office 365 Pro Plus open an elevated cmd prompt.
- Map a drive to the share. For example net use K: \\servername\office365pro
- Change the directory to K:\Office\Office.
- Issue the following command setup.exe /configure configuration.xml
- If an error occurs check the Officesetup.txt log in %temp% on the client. If no error occurs proceed to step 6. I have seen errors due to some files missing from the source. If this occurs repeat step 15 in the downloading section above.
- Enter in the email address of the user who has an Office 365 subscription and will be using Office 365 Pro Plus on this computer and click Next. Alternatively you can click on the Enter a product key instead option if you wish to activate it with a product key.
- You can actually close the window at this stage and the install will complete. It just won’t be activated. You will be prompted to activate whenever an Office Pro Plus application is launched.
- Have fun going through “Welcome to your new Office”.
- Start using Office 365 Professional Plus.
Share the post "HTTP Error 500.19 – Internal Server Error after installing WSUS"
Windows 2012 server with an existing IIS install and a couple of websites. WSUS was then installed on this server using the custom site option.
WSUS and all of the other sites except one functioned correctly after the install.
When attempting to browse to the non working site a HTTP Error 500.19 error was displayed with the error source being DynamicCompressionModule.
It would appear that the installation of WSUS enabled this compression scheme and one of the sites was not compatible with this compression.
To turn off the compression scheme use the following command from an elevated command prompt on the server:-
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
Note: Compression schemes are registered globally so this command will turn it off for all sites on the server. If you need to re-enable the scheme use this command:-
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']
Thanks to anilr at http://forums.iis.net/t/1149768.aspx for this information.
Share the post "Unable to open TrendMicro WFBS 8 Console – Service Unavailable"
When attempting to open the TrendMicro WFBS 8 Console you receive a service is unavailable message. HTTP Error 503. The service is unavailable.
To resolve this issue:-
- On the TrendMicro server open IIS Manager
- Expand SERVERNAME
- Select Application Pools
- The OsceAppPool will be stopped. Attempting to start the pool results in a start and stop.
- Right click on OsceAppPool and select Advanced Settings.
- Scroll down to Process Model.
- Select the options for Identity
- Change to “Built-in account” and select Local System
- Click on Ok x 2.
- Right click on OsceAppPool and select Start
- Attempt to access the TrendMicro console.
If this does not resolve the issue you may need to create a new Application Pool which is documented in this TrendMicro article.
Share the post "Comparing Microsoft Office 2013 licensing options (with cost calculator)"
With the push by Microsoft (and almost everyone in the industry) to use Cloud services and therefore subscriptions it has become increasingly more difficult to determine the best method to license Microsoft Office 2013 for businesses.
Options available today include:-
- Purchase a Retail box (Full Packaged Product)
- Volume Licensing
- Office 365
Each option has its features and limitations which impact the decision making process.
I’ve created a spreadsheet to assist with calculating the cost of each licensing option with totals at the 3 and 5 year mark. It also includes the major differences between the options. Only 2 of the Microsoft Open volume licensing options have been listed but feel free to download the spreadsheet and modify it however you like.
The pricing that has been entered is Australian. Enter pricing for your region and adjust the tax rate if necessary.
It is a work in progress so if you find it of use you may like to check back here again in the future.