- Setup a second store server that can be activated if necessary to act as a replacement store server
- Pharacy data
- Terminal -> Store Server -> Head Office -> Store Servers -> Terminals
- Regular POS Data
- Terminal ->HO ->Terminals
- Changes to new store server to get it to match the old store server it's replacing
- Change new computer name to old server computer name
- Change new sql instance name to old instance name
- In NAV Admin Console, change the following to the old store database name and for all instances
- Database Name
- Database Service company
- Services Default company
- Set pharmacy prescription numbering last number to the last prescription number received at HO from this store + 100 to avoid duplicates of prescriptions that may not have been transmitted before the old server went down
- Set Issuer Numbering last number to the last Issuer number at HO from this store
- Set Pharmacy Customer last number to the last Pharmacy customer number at HO from this store
- Update Web service setup in new Store Server database to match old store server web service setup
Pre-Requisites
- Install SQL 2008R2 or higher (Express can be used)
- Enable TCP IP protocols
- Change service account to sqldb account
- Install NAV, LS and Data Director
- Create NAS Instance: Same ports as old store server, point to company db
- Set services time zone to server time zone
- Set default company to the company db
- Create Web Service Instance: Same ports as old store server, point to company db
- Set services time zone to server time zone
- Set default company to the company db
- Enable soap, set message size 2048
- Copy Images Folder to new machine
- From \\pharmacy
- To c:\
- Copy pharmacy dll's to new machine
- From \\Pharmacy DLL
- To c:\program files(x86) Microsoft dynamics nav\71\Role Tailored client\add-ins\
- Copy Scanner dll to new machine
- From \\PMS Scanner DLL
- To
- Restore Last Store Database Backup into SQL
No comments:
Post a Comment