Update Software Inc South Highway 101 Hopland, CA Phone: 707/ Fax: 707/

Transcription

1 Update Software Inc South Highway 101 Hopland, CA Phone: 707/ Fax: 707/ Instructions for Replacement of VinNOW Database Machine Except in the case of a system crash, an appointment must be made with VinNOW Support at least 24hrs prior to the requested time for assistance in restoring the database. VinNOW support is only available Mon-Fri 9 to 5 PST and only with an appointment for database restore. The customer or the customer s IT support is responsible for installation of Microsoft SQL Server and all steps with the exception of restoring the database and should completely read the following instructions prior to attempting a DB move. If you have any questions about specifications or need more information please visit the Client Center on our website for our documentation ( Troubleshooting and computer requirement documents should all be reviewed prior to starting a database conversion. Do Not copy over the old VinNOW_DB folder, SQL Database, Registration Entries or VinNOW Program File this will cause connectivity issues. These items need to be created fresh on the New Server using the following steps: 1. Prepare the new server machine to include: Make sure the machine has the appropriate OS per our specifications- no home editions and is current on Windows updates. The Windows user that is logged in when SQL Server and VinNOW is installed must be an Administrator, password protected, and User Account Controls should be turned off SQL Server 2008R2 Native Client must be installed. You can find this download at: (subject to change without notice by Microsoft). Open the section for Install Instructions and scroll until you see the native client option. Chose the x64 or x86 sqlncli.msi download as appropriate for your system..net Framework version 4.5 must to be installed. You can find this download at: (subject to change without notice by Microsoft). 2. Install SQL server 2012 Express with Management Tools (if under 10 client workstations, full SQL Server if more than 10). Although SQL can handle up to 10 workstations, the amount of workstations that can be actually used on your network may vary depending on your network configuration, speed, and components. If there are performance or connectivity issues you may need to install the full version of SQL as it is more robust and will be able to process faster. The executable that you download to accomplish installing SQL Express can be located at: (subject to change without notice by Microsoft). 1

2 Download the appropriate executable for your system, 32 or 64 bit which should be named SQLEXPRWT_x86_ENU.exe or SQLEXPRWT_x64_ENU.exe. Take all defaults for the install. Under the database configuration make sure Windows Authentication is selected. Note: SQL Instance names must be 16 characters or less Once the installation is complete, in your start menu, find the SQL Server Express 2012 folder and go into Configuration Manager. If you have a windows 10 machine you will need to path to: SQLServerManager11.msc to open the configuration manager. Under SQL Server Services make sure the SQL Server Database Engine and the SQL Server Browser have a State of Running the Start Mode should be Automatic and the Login should be NT AUTHORITY\NETWORK SERVICE. The SQL Server Agent does not matter for this application and does not need to be running. While still in Configuration Manager check under the SQL Server Network Configuration that the Protocols have the Shared Memory Named Pipes and TCP/IP all set to Enabled Exit the Configuration Manager and go into SQL Server Management Studio on the start menu to make sure you can connect to the instance. 3. Reboot the machine at this time. 4. Turn Off Simple File sharing or Use Sharing Wizard Which is located under the Control Panel, folders options pick the view tab and scroll down until you find the Use Sharing Wizard box and make sure it is un-checked. Then click apply and exit the screen. 5. On the Computer where SQL Server and VinNOW is installed the Windows Firewall must be configured to allow SQL access. At a minimum this means exceptions must be provided for the SQL Server engine, "sqlserver.exe", and the SQL Server Browser, "sqlbrowser.exe", or alternatively; SQL Server TCP port 1433 and SQL Browser UDP port Make sure that in whatever Virus protection you are using VinNOW and SQL Server are listed as exceptions and can communicate with each other and access the network and internet without being restricted or filtered. 7. Set up New VinNOW folders. These folders should be set up and named exactly as specified in this document. They should only contain the information that is placed in them by the VinNOW program. Primary VinNOW Folder: On the Root drive create a folder named VinNOW_DB. If you have a data drive you can use this drive, however, the VinNOW_DB folder should be in the root drive and not placed within another folder. Share the VinNOW_DB folder and using advanced sharing give everyone full control. Under the Security Tab make sure all Groups/Users have full control. This will become the primary folder where the database and associated folders will reside. 2

3 Inside the VinNOW_DB folder create a folder named Update. This will be the folder where the Setup.exe and VinNOW.msi will reside. VinNOW_Logos Folder: Create a folder in the same Root drive named VinNOW_Logos. Share the VinNOW_Logos folder and using advanced sharing give everyone full control. Under the Security Tab make sure all Groups/Users have full control. This folder can be used by you to store Logos for the program and the printers as it is not used by the VinNOW program. This is the only VinNOW folder that users should store information and pictures into. 8. On the old Server, backup the database by logging into VinNOW and creating a backup via the VinNOW File Menu. Place this backup zip file into the VinNOW_DB folder on the new server and extract the contents. The extracted file should be VinNOWDB.Bak 9. While logged into the VinNOW program, go to the SetUp Menu, System Options, System Option Settings tab and all the way at the bottom of that area you will see the Registered Company Name and Serial Number. Copy these exactly as they are displayed so that you have them available for use when you install the program on the new server. You should not retain these credentials for future use as they may change as program options change. 10. Move the Setup.exe and VinNOW.msi from the old VinNOW_DB\Update folder to the new server VinNOW_DB\Update folder. 11. From the VinNOW_DB\update folder on the new server run the setup.exe to install the program. 12. Contact VinNOW Support for assistance in restoring your database from the backup file before continuing. 13. Once your database is restored and your system is set up on the new machine, it is critical that you stop the SQL services on the old server so there is no chance a client machine can connect to the old database. On the old server, In the SQL Configuration manager, SQL Server Services, make sure the SQL Server Database Engine and the SQL Server Browser have a state of stopped the Start Mode should be disabled. Rename the VinNOW_DB folder on the old server to OldVinNOW_DB We recommend you not delete the old VinNOW_DB folder for 30 days so you have a backup setup for the VinNOW program until you are sure your new system is functioning properly. After that time, you can just delete this folder if you wish. Once the Server Machine is installed you will need to point the client machines to the new server. 1. If in a workgroup, make sure the windows user profiles of the client machines are recreated on the new server machine exactly including passwords, so the server can determine the user permissions of the client machines. If in a Domain this is not necessary as the User permissions are determined by the Domain. 2. On the new server, log into VinNOW to register the Windows User names of the client machines. Go to the SetUp Menu, and in the menu below System Options you will see register SQL 3

4 Server Logins. You will then see a table that you can add the user names to. Enter login names (e.g. computername\username, the computer name being that of the server machine) and make sure that the windows user is in both the left and right hand columns. This user entry application can also be found in C:\Program Files (x86)\vinnow\vregsqlu 3. The client machines must also have.net Framework version 4.5 installed. 4. Client machines must connect to the server via UNC pathing. 5. For machines that were VinNOW client machines prior to the server change you must re-point the machine to the new server. In the C:\Programdata\Update Software Inc\VinNOW folder there is a VinNOW.config file. Open the file using Microsoft Visual Studio tools for Applications and edit the DB Path to reflect the correct path to the new server machine. Be very careful not to delete any quotation marks or other necessary characters. Do not open/save with notepad or word. If you do not have Microsoft Visual Studio tools for Applications, delete the VinNOW.Config file and attempt to log onto the program which will create it. You will be prompted to enter your Registered Company Name and Serial Number again and a valid UNC database pathway. Note: The ProgramData file is normally a hidden file on most machines and you will need to path to the file. If the client machine still does not connect, attempt to surf to the database machine VinNOW_DB folder by using the pathway you have entered to see if the machines can connect. If you have further issues, refer to our Checklist for Connectivity Issues and other troubleshooting documents. 6. For new client computers that have never had VinNOW, you must first install SQL Server 2008 R2 Native Client prior to installing VinNOW (used for both 2008 R2 and 2012 SQL installations). You can find this at: (location subject to change by Microsoft) Open the section for Install Instructions and scroll until you see the native client option. Chose the x64 or x86 sqlncli.msi download as appropriate for your system: 4

5 7. If VinNOW is currently installed on the machine, Uninstall VinNOW by going to the start menu, all programs, Update Software Inc, VinNOW, Uninstall VinNOW and walk through the wizard. To reinstall VinNOW reach across network and run the SetUp.exe located in VinNOW_DB\Update folder on the server. Walk through the wizard. 8. If VinNOW is not currently installed on the machine, install VinNOW from the new server machine by reaching across network and running the setup.exe located in VinNOW_DB\Update folder on the server. Walk through the wizard. 9. Launch and sign into VinNOW to verify the machine can connect. If VinNOW on the client machine can not connect and open the program, refer to our Checklist for Connectivity Issues document on our website. 5