TechShizz | All posts tagged 'Migration'

Install ADS Server for PICs by Pellcomp

Advantage Database Server (ADS) is a low-maintenance database server that sits alongside the PICS data files, and provides a connection to the database that is quicker and more reliable than standard Windows file sharing.
Installation Instructions

These instructions should be completed on the server where the PICS data is located.

Get your serial key from Pellcomp.

First, download this install shield and start the installation process. If asked if you want to remove the previous installation you should choose yes. You can install the software in any location provided this is on the machine where the PICS database is located.

The installer will prompt you for a serial and validation code which are listed above. Do not enter your validation code into the replication box, leave this blank! Enter the Registered Owner (your company name) & Startup Type (this should be Automatic).

Once the installation is complete, you should ensure that all installation windows are closed (click “Finish”), and the Advantage Configuration Utility will appear. You should see the screen shown below:

 If the Service Up Time shows “ADS Service not started”, click the “Start Service” button (bottom of the window) to start the service. You can then click “Exit”, which will leave the service running.

If you encounter any errors please contact the Pellcomp support desk on 01603 492620.

Security Settings

By default the Advantage Database Service runs using the built-in SYSTEM user account. This account must have full read/write/delete permission to the folder containing the PICS Database files.

Client machines need to connect to the ADS service on the server using UDP port 6262. You may therefore need to open this port on any firewalls you may be running.

PICS Settings (client machine)

  • Upgrade PICS to the latest version and start a copy of PICS. From the login screen select Help -> Options -> Allowed ADS Modes -> Remote. PICS will then restart in client server mode.
  • If you have PICS installed locally on each client machine you will need to set "Remote" on each copy of PICS.
  • If PICS is communicating with the server, after logging in you will see “C/S” after “PICS” in the PICS title bar.
  • Please note that you cannot mix modes. That is if one copy of PICS is open in the traditional Local Server mode then you won’t be able to log into any of the Client Server enabled copies of PICS and vice versa.

Steps to Migrate PICs application by Pellcomp

Backup the data:
The most secure way to move the data is to create a PICS backup and then restore the backup once PICS is installed on the new server. To create a backup, please follow these instructions...

From the PICS logon screen, go to the Tools menu and select Backup Database (Data Only).
When the backup screen appears, click on Start.
When prompted, save the file to a network share that is accessible to both servers.
Transferring via removable media is also possible at this point.

Copy miscellaneous files:
It’s possible that staff have saved various reports and files into the PICS Software or Data folders.  In particular you should look for any files in the Software folder which start ‘ILP_’ or end with a .ahl extension.  Any such files need to be copied and moved over to the new Software folder once it’s been created. 

If you have the optional Scheduled Reporting module then you will need to make a copy of the SchedRepData sub-folder which is also in the Software folder.

In addition to these standard PICS files, staff may well have saved general reports and documents so it’s best to check with them or look out for large numbers of Office documents which may require moving.

Install PICS Software on the new server:
Download the latest copy of PICS from the following link:
http://www.pellcomp.co.uk/pics_dl.php
Create a folder on the server called 'Pellcomp' and within there a folder called 'Software'.
Install the software on the server in the new 'Software' folder.
Once installed you will be prompted for the data path. Leave it there for now and go to the ‘Move the data’ section below.

Move the data:
Create another new folder in the 'Pellcomp' folder called 'Data'.
Set the folder permissions so that all users and the System account have Full Control.
Copy the backup from the network drive to the new 'Data' folder.

Restore the data:
Go back to the PICS screen and click on the Browse button.
Navigate to the Data folder we created earlier and click Select. Please note that the address used here needs to be an address that means the same to the client computers, so either a UNC path or a common mapped network drive.
When warned that no database exists, click on Accept.
Click the Restore button and then click on the folder icon (3 dots).
Find the backup file in the DATA folder and click on Open.
Click on Restore.
Confirm the details on screen and then click Yes.
The database will now restore.

Install ADS:
Please follow the instructions in the attached document.

Re-Create the client shortcuts:
Go to the 'Software' folder you created and installed the software into earlier.
Create a shortcut to PICS.exe in this folder. This is the shortcut that the client PCs will need on their desktops.

Finally:
You can now logon, but when you try to access the data you will be asked for a licence.  Please enter:

[PLEASE EMAIL PELLCOMP FOR YOUR LICENCE INFO]

The last thing to do is update the software to make sure it is fully up to date.
To do this follow the instructions below:

  1. Make sure everyone is out of PICS.
  2. Get to the Login Screen.
  3. Go to the ‘Tools’ Menu item, then ‘Software Updates’.
  4. Enter your usual username and password, when prompted. This is actually a password permission to be able to run Software Updates so it may be needed to be added to your user in Password maintenance, by the PICS supervisor.
  5. You should get another window pop up and the PICS login screen close. In this new window click on ‘Next’.
  6. This should then check the versions available and give you a list of the parts of PICS that need updating, click ‘Next’ again.
  7. This will run through downloading the different files. After it done click on ‘Next’ again.
  8. Click ‘Next’ on the next screen, which talks about Local Network Updates.
  9. This will then go through installing the updates and will display the message ‘Updates installed, press OK to return to PICS’. Click ‘OK’.
  10. Log into PICS as normal.

Disable Autodiscover for Office 365 Migration

When migrating to Office 365 the internal outlook users are not able to use autodiscover.

This is because the internal exchange server also uses autodiscover in IIS.

Use this description to remove the internal AutodiscoverVirtualDirectory

Be sure that this is the proper migration plan for you’re organization!

1. Open an elevated command prompt and back-up the IIS configuration (Just in case !):

cd %windir%system32inetsrvappcmd.exe add backup “Before Removing Autodiscover”

2. Open an elevated Exchange Management Shell and retrieve the current autodiscover virtual directory:

Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl, Identity

Copy the Identity value to the clipboard.

3. In the Exchange Management Shell, remove the autodiscover virtual directory:

Remove-AutodiscoverVirtualDirectory -Identity “ALPHAAutodiscover (Default Web Site)”

When you’re identity contains a space, use the quotation marks ”

You will have to confirm by typing a “Y”.

4. Check that the autodiscover virtual directory is gone:

Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl, Identity

This should now return nothing.

5. Now, with Outlook running on a desktop, hold the Ctrl button, right-click on the Outlook icon in the system tray, and select Test E-mail AutoConfiguration. Enter your email address and password and click the Test button. The results should come from the Office 365 server.

Migrating Server Roles with SmigDeploy

Get-WindowFeature - Name migration

Install-WindowsFeature -Name migration

cd \windows\system32\servermigrationtools

.\smigdeploy.exe /package /architecture /amd64 /os WS12R2 /path C:\Migration

#copy the Smig files to the Source Machine
Copy-Item -Path C:\Migration\SMT_ws12r2_amd64 -Destination \\srv2012-lab\c$\Migration

.NET 3.5 is required on the source machine for this to work, so the first step (if it is not already installed) is to install it.

#Check is .NET3.5 is installed
Get-WindowsFeature -Name net-framework-core

#Install .NET 3.5 if required. You will need a 2012R2 ISO mounted for the source files

Install-WindowsFeature net-framework-core -source D:\sources\sxs

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

#Stop DHCP (the role we're migrating)
Stop-Service -Name DHCP

#View roles and features eligible for migration
Get-SmigServerFeature

#Export the migration data
Export-SmigServerSetting -FeatureID DHCP -Path c:\migration\DHCPMigration -verbose

#Finally copy this exported data back over to the target server
Copy-Item -Path C:\migration\DHPCMigration -Destination \\srv2016-lab\c$\migration

Back over on the Target server we now need to Import the settings

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

#Install DHCP role and import settings
Import-SmigServerSetting -FeatureID DHCP -Path C:\migration\DHCPMigration -verbode -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