Category: Server 2012 R2 Essentials

Unable to add a new Backup Destination via the Windows Backup Console

Unable to add a new Backup Destination via the Windows Backup Console

By | | Comments 0 Comment

Problem:

Unable to add a new Windows Backup Destination to an existing Windows Backup Schedule via the Windows Backup mmc snap-in (Console).

Resolution:

Use wbadmin in an Elevated Command Prompt to add the new Destination Drive to the Backup Schedule.

Run the following command in an elevated command prompt to determine the Disk Identifier of the new disk:

wbadmin get disks

Based on the output, locate the disk that will be added to the scheduled backup. Make a note or copy the Disk Identifier (including the brackets). Be sure to copy the correct ID! If you don’t you could end up formatting another drive. The output will resemble the following:

Disk name: xxxxxxxxxxx
Disk number: x
Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Total space: xxx.xx GB
Used space : xxx.xx GB

Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the “AddTarget” parameter.

wbadmin enable backup -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

When you receive the following prompt, type Y for Yes.
“Do you want to enable scheduled backups with the above settings?”

Once this has been completed, open up the Windows Server Backup Console and make sure that you can see the new.

The only irritating thing about adding a drive via this method is that it allocated a long name to the disk. It’t not really a problem, its just annoying if you have a number of backup drives labelled as ‘Backup 1’ ‘Backup 2’ etc and then you have a generated disk name that doesn’t suit.

Microsoft KB Article:
https://support.microsoft.com/en-us/help/2009365/error-message-when-you-try-to-add-an-additional-disk-to-a-scheduled-backup-the-filename,-directory-name,-or-volume-label-syntax-is-incorrect

Windows 10 – Windows Explorer not responding when creating or renaming a folder on a Server 2012 Essentials R2 network share

Windows 10 – Windows Explorer not responding when creating or renaming a folder on a Server 2012 Essentials R2 network share

By | | Comments 0 Comment

Problem:

I recently had an issue with a Windows 10 PC. Windows Explorer stops responding when creating or renaming a folder on a Server 2012 Essentials R2 network share.

Client Spec:
Windows 10 64-Bit
Version 1607
Build 14393.351
4GB RAM
i5 Processor

Issue explained:

When the user tries to create or rename a folder on a network share (UNC Path/Mapped Drive or IP Address), Windows explorer stops responding for about 30-60 seconds. Eventually the folder does get created or renamed. Viewing this from the server shows the old folder name until about 30-60 seconds later. No error is displayed client end other than the not responding of Windows Explorer.

Resolution:

For me the only resolution for this issue was to stop and disable the ‘Windows Search’ service on the server. As soon as the service is disabled the folders can be created and renamed without delay. Restarting the service caused the problem to come back immediately.

As far as I am aware, Microsoft has yet to create a patch for this issue.

Unable to set up Office 365 integration on Windows Server 2012 R2 Essentials

Unable to set up Office 365 integration on Windows Server 2012 R2 Essentials

By | | Comments 0 Comment

I’ve previously came across a problem with integrating the Windows Server Essentials 2012 Dashboard with Office 365. I’m posting the problem and solution here as it has helped some other users on a few forums.

Problem:

When running the Office 365 integration wizard in the Windows Server 2012 R2 Essentials dashboard the wizard runs for a very long time, and returns the following error:

“An unknown error occurred. Make sure that the computer is connected to the internet, and the try again. If you continue to to experience, restart the server and then try again”

My Solution:

After checking through the log files (C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log) I found the following:

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: The remote server returned an error: (404) Not Found. —> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.WebClient.DownloadFile(Uri address, String fileName)
at Microsoft.WindowsServerSolutions.O365Integration.SharePointManagementUtils.InstallCSOM()

I resolved the error by installing the ‘SharePoint Server 2013 Client Components SDK‘ which contains the CSOM modules. See here:

http://www.microsoft.com/en-gb/download/details.aspx?id=35585

Once this had been installed the Integration wizard worked correctly.

Hope that this helps.

Using the Connector with a PC that is already domain joined, to add it into the Essentials Dashboard – Server 2012 R2 Essentials

Using the Connector with a PC that is already domain joined, to add it into the Essentials Dashboard – Server 2012 R2 Essentials

By | | Comments 0 Comment

I recently came across a problem whereby a number of PCs had been manually added to a domain within a Server 2012 R2 Essentials environment.  The customer wanted to be able to connect to the computer remotely via Remote Web Workplace.  Therefore the connector needed to be installed.

When you try and install the connector on a PC that is already joined to the domain you get an error saying that a duplicate name already exists on the network (yes, the PC you’re on!).

To resolve the error you need to add a registry key/hack on the client machine which bypasses the domain join section of the wizard.  See below:

reg add “HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment” /v SkipDomainJoin /t REG_DWORD /d 1

Original Article were the solution was posted:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/603bf59c-4b1f-4fa1-817e-8d0a6bbf236f/how-to-join-a-client-pc-to-ws2012e-r2-thats-already-a-member-of-another-enterprise-domain-using-the?forum=winserveressentials