When copying data, if the folder naming structure to long you may come across the following error.
In order to get around this you can either do one of two options:
- Rename to a smaller naming structure
- Use robocopy.exe to copy the data over to the new location – %Systemroot%\System32\robocopy.exe
We are in the process of removing our old WSUS server that has faithfully served our client for main years. However now it is time to restore the servers pointing to this box back to the default value of Windows Update.
You can do this either with Powershell or editing the registry.
- Stop the Windows Update service
- Open regedit
- Find the following key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\
- Right-Click and delete the registry key Windows Update
- Restart the Windows update Service
Yesterday, I was in the process of uninstalling the UM Role from an Exchange Server 2010 Server which we had set to decommission now that we are migrating to Exchange Server 2016.
Running Setup /mode:Uninstall from the following directory C:\Program Files\Microsoft\Exchange Server\V14\Bin – I ran into my first error.
The tmlisten service is our Officescan Antivirus which was running at the time. I promptly unloaded the service and tried the uninstallation process again which generated the following error:
C:\Program Files\Microsoft\Exchange Server\V14\Bin\ManageScheduleTask.ps1 is not recognized as the name of a cmdlet, function, script file, or operable program.
I found a possible solution here:
Moved the ManageScheduletask.ps1 and ManageScheduletask.strings into the Bin directory from the Scripts directory. Apparently it may be a bug, re-ran the uninstalltion process but unfortunately the process failed again.
This time I was in a far worse situation since I had a half uninstalled version of Exchange on my UM server. The application was no longer visible in Programs and Features but the directory was clearly there (albeit missing files) and running Get-ExchangeServer clearly displayed the Exchange server in question.
I didn’t want to manually remove the server entries with ADSIEdit so I reinstalled Exchange Server 2010 SP3 only (we were at CU level 18 ). Then reran the uninstallation process again.
The process failed yet again this time Setup could not find the following file ConfigureNetworkProtocolParameter.ps1 under the Scripts directory. Checked this location and indeed the file was missing because I cross referenced it with another Exchange server. I copied this file into the directory reran the process and was finally able to perform a clean uninstallation of Exchange.
The simple straight forward method to truncate logs in the occasion where you find yourself running out of disk space and do not have additional free space to spare.
Open SQL Studio > Select the database in question > Right click and Select Properties
From the Database Properties Window select Option and change the Recovery model to Simple.
Then Right click the database and select Tasks > Shrink > Files. Change the File Type to Log > Select OK
This will truncate the .ldf file.
Microsoft has provided scripts to help with Public Folder management, in the event you need to remove a Public Folder Database from replication to the scripts directory of your installation path for Exchange.
Example: C:\Program File\Microsoft\Exchange Server\V14\scripts
Run the following:
.\RemoveReplicaFromPFRecursive.ps1 -TopPublicFolder “\” -ServerToRemove “NameofYourMailboxServer”
This will take some time to replicate. Once complete run the follow command to verify that all Public Folder replicas have been removed from this Public Folder Database.
Get-PublicFolder -Recurse | ft Name,ParentPath,Replicas
The replica for the given Public Folder Database should be removed. You can then proceed with removing the Public Folder Database.
Remove-PublicFolderDatabase “Name of your “PublicFolderDatabase”
On your remote machine open Powershell – Populate a variable with the credentials you will use to connect to your Exchange server
Next type the following command to create a new session with the given credentials
$session = New-Pssession -ConfigurationName Microsoft.Exchange -connnectionuri http://yourservernameFQDN/powershell -authentication Kerberos -credential $credentials
Once this command is complete import the Exchange Powershell module to your machine using the following command.
Using the EMC under Server Configuration > Select Unified Messaging > Select Properties
From the Properties Window select the UM Settings tab > Select the Dial Plan and Remove.
Using Powershell Run the following Command:
Set-UMServer -Identity <ServerName> -DialPlans $null