TechShizz | Tech Guides

Migrate Server Roles with SmigDeploy

 

# view server migration tools feature
Get-WindowsFeature -Name migration

# install windows server migration tools
Install-WindowsFeature -Name migration

# navigate to smt directory
cd \windows\system32\servermigrationtools

# generate package for source machine
.\smigdeploy.exe /package /architecture amd64 /os WS12R2 /path C:\Nuggetlab

# copy package over to source machine
Copy-Item -Path c:\nuggetlab\SMT_ws12R2_amd64 -Destination \\srv2012-nug\c$\nuggetlab -Recurse


### complete steps on SRV2012-NUG (source machine) before going further ###

# import smig cmdlets into session
Add-PSSnapin Microsoft.Windows.ServerManager.Migration

# install DHCP role and import settings!
Import-SmigServerSetting -FeatureID DHCP -Path c:\nuggetlab\migration -Verbose -Force

 

Migrate Server Roles with SmigDeploy

 

# view server migration tools feature
Get-WindowsFeature -Name migration

# install windows server migration tools
Install-WindowsFeature -Name migration

# navigate to smt directory
cd \windows\system32\servermigrationtools

# generate package for source machine
.\smigdeploy.exe /package /architecture amd64 /os WS12R2 /path C:\Nuggetlab

# copy package over to source machine
Copy-Item -Path c:\nuggetlab\SMT_ws12R2_amd64 -Destination \\srv2012-nug\c$\nuggetlab -Recurse


### complete steps on SRV2012-NUG (source machine) before going further ###

# import smig cmdlets into session
Add-PSSnapin Microsoft.Windows.ServerManager.Migration

# install DHCP role and import settings!
Import-SmigServerSetting -FeatureID DHCP -Path c:\nuggetlab\migration -Verbose -Force

 

Migrate Server Roles with SmigDeploy

 

 

# view server migration tools feature
Get-WindowsFeature -Name migration

# install windows server migration tools
Install-WindowsFeature -Name migration

# navigate to smt directory
cd \windows\system32\servermigrationtools

# generate package for source machine
.\smigdeploy.exe /package /architecture amd64 /os WS12R2 /path C:\Nuggetlab

# copy package over to source machine
Copy-Item -Path c:\nuggetlab\SMT_ws12R2_amd64 -Destination \\srv2012-nug\c$\nuggetlab -Recurse


### complete steps on SRV2012-NUG (source machine) before going further ###

# import smig cmdlets into session
Add-PSSnapin Microsoft.Windows.ServerManager.Migration

# install DHCP role and import settings!
Import-SmigServerSetting -FeatureID DHCP -Path c:\nuggetlab\migration -Verbose -Force

 

Manually Uninstall Sage 50 Accounts

Problem

Manually Uninstall Sage Accounts because the uninstaller leaves remnants of the application in various locations.

Solution

Using the Control panel uninstall Sage 50 (and the data service if installed)

Reboot

Repair .net

This step is not always needed, you only need it if .net is damaged and it takes a while you might skip this if you feel lucky

use the .net repair tool http://www.microsoft.com/en-gb/download/details.aspx?id=30135 to repair .net

Program Files

Delete the following directories

C:Program Files (x86)SageAccounts (The installation folder, this could be different if you did a none standard install)
C:Program Files (x86)Common FilesSage Line50
C:Program Files (x86)Common FilesSage Report Designer 2007
C:Program Files (x86)Common FilesSage SBD
C:Program Files (x86)Common FilesSage SData
C:Program Files (x86)Common FilesSage Shared
C:Program Files (x86)Sage EBanking

If you are using a 32 bit operating system then the above path will be Program Files not Program Files (x86)

If you have your OS installed on a Drive other than C: the The drive letter will need changing

You may need admin rights to delete these folders, you may need to switch off UAC

If you have problems deleting any of the above then it is possible that the services have not been uninstalled properly and or stopped rebooting would normally fix this.

You can force the services to stop as follows 

  1. Press the Windows Key + R on your keyboard - enter Services.msc in the run box and press Enter.
  2. Scroll down to the services starting with S 
  3. Right-click each of the Sage services and choose Stop.

Retry deleting the files and continue.

Sage Query Engine

At the command Command Prompt

cd
del sage.query.engine.datasource* /s
exit

Sage ini and sglch32.usr

Rename the following files by appending .old

C:Users%user%AppDataLocalVirtualStoreWindowsSyswow64sglch32.usr
C:WindowsSYSWOW64sglch32.usr
C:ProgramDataSageAccountssage.ini

on 32bit systems 

C:Users%user%AppDataLocalVirtualStoreWindowsSystem32sglch32.usr
C:WindowsSystem32sglch32.usr
C:ProgramDataSageAccountssage.ini

Assembly

Files in the Assembly folder should be uninstalled. right-click > Uninstall. 
C:WindowsAssemblyantlr.runtime
C:WindowsAssemblysage.*

You may find, some will not uninstall, this is not uncommon do what you can.

System Folder

From the windows system folder C:WindowsSysWOW 

Delete these files

repdes.cnt
RepDes32.exe
SageBankBalances.tlb
SageBankPayments.tlb
SageBankReconciliation.tlb
SageEBanking.tlb
SageEventHandler.Config
SageEventHandler.exe
SageFolderBrowser.dll
SG3D32.DLL
sg50Ps32.dll
SGAPPBAR.DLL
SGCDLG32.DLL
SGCOM32.DLL
SGCtrlEx.dll
SGDT32.DLL
SgESchema.xsd
SGHELP32.DLL
SgHmZLib.dll
SGINTL32.DLL
SGJPEG32.dll
SGLCH32.DLL
SGLCH32.USR
SGLIST32.DLL
SGLOGO32.DLL
SGOEdit.ocx
SGOList.ocx
SGOPopDg.dll
sgopopup.ocx
SGOSize.ocx
SGOTBar.ocx
SGRegister.dll
SGRegister.tlb
SGRep32.dll
SGSchemeDefault.dll
SGSchemeManager.dll
SGSchemeXml.dll
SGSchemeXP.dll
SGSTAT32.DLL
SGSTDREG.dll
SGStdReg.tlb
SGTBAR32.DLL
SGTOOL32.DLL
SGWebBrowser.dll
sdoEng*.*
S??DBC32.dll  - Replace ?? with your version number eg 20 for V2014 13 for V2007 there may be several older versions present

If you are using a 32 bit operating system then the path will be C:WindowsSystem32 not C:WindowsSysWOW64

More Sage Files in the Windows System folder

There may be other files from Sage in the system folder

Turn on the Company Column

Click on the company heading to sort by it.

Look for any Files with these company names and delete them

Sage (UK) Limited
Sage (UK) Ltd
Sage
The Sage Group plc
SAGE software Ltd

Delete User Appdata

Delete the following folders where %user% is the users directory

C:Users%user%AppDataLocalSage
C:Users%user%AppDataLocalSage_(UK)_Limited

If you are using XP or older you need to adjust the paths eg C:Documents and Settings%user%Application DataLocalSage

Delete Temporary Files

Run the windows "disk cleanup" tool

or use Ccleaner from pirisoft 

Delete Data folders

Note: You are deleting your data in this step make sure you have a backup or move the folder somewhere else (you might try renaming them rather than deleting them if you are concerned about your backups)

In most cases, this is not normally needed.

C:ProgramDataSage

If you are using XP or older C:Documents and SettingsAll UsersApplication DataSage

Sage Drive Removal

Stop the Sage Services

  • Sage 50 Accounts Control
  • Sage 50 Accounts Service

Delete everything in the collaborate folder

  • 32 bit: C:WindowsSystem32configsystemprofileAppDataLocalSageSSBAccountsCollaborate
  • 64 bit: C:WindowsSyswow64configsystemprofileAppDataLocalSageSSBAccountsCollaborate

Delete the database files

C:Program Files (x86)SageAccountsServiceV22Sg50Svc_v22.sqlite3
C:Program Files (x86)SageAccountsServiceV22Sg50Svc_v22.sqlite3-Shm
C:Program Files (x86)SageAccountsServiceV22Sg50Svc_v22.sqlite3-wal

C:Program Files (x86)SageAccountsSg50Svc_v22.sqlite3
C:Program Files (x86)SageAccountsSg50Svc_v22.sqlite3-Shm
C:Program Files (x86)SageAccountsSg50Svc_v22.sqlite3-wal

Delete sage drive files

C:ProgramDataSageAccountsSageDrive

Uninstall Finished

Get Windows up to date

Reference, Links and Imges

 http://www.makingithappen.co.uk/sage-50-guides/clean-reinstall.htm

PPTP VPN Stuck on Verifying username and password when dialling a Microsoft Routing and Remote Access Server

Problem

When dialling a PPTP VPN, the dial up fails and hangs on verifying username and password. It then produces an 806 error.

Solution

In my case, port 1723 was open and i could prove this by viewing the router and by telnet to the IP and port 1723. The issue stood out as an authentication problem as this is where the process hangs. 

The solution was to enable "Routing and Remote Access (GRE-In) on the domain profile of the RRAS server. 

No idea how this turned itself off, but it did.