Presentation on theme: "IT Best Practices for Sage Timberline Office (STO)"— Presentation transcript:
1IT Best Practices for Sage Timberline Office (STO) October 14, 2011
2IntroductionsChris Elekonich Professional Services Manager Rod Hatley Technical Services Manager – Atlantic Division
3About Aktion Partnering with Customers for Growth and Profitability Founded in 1979Over 4,000 Customers in the Midwest , Mid- Atlantic and SoutheastProfitable, Stable Growth90+ Employees5 Office Locations – Maumee, OH (HQ), Columbus, OH, Charlotte, NC, Indianapolis, IN, Aurora, ILComplete IT Services Including Network Infrastructure, Custom Applications, Application Hosting
4Industries of Expertise Architects and EngineersProfessional Service Businesses and OrganizationsConstruction and Real EstateSupply ChainNot for Profit
5Network Engineering 15 Network Engineers 12 States in the Midwest and Atlantic CoastRemote Support – 80%Managed ServicesHostingRemote Monitoring and System Admin
6Network Engineering Network Assessments Security Assessments and Vulnerability TestingVirtualizationDisaster Recovery and High Availability“Break Fix”
7Software Engineering Custom Programming Integration to other applications and Excel and WordAktion Authored ApplicationsePayStub, eTimeCardProductivity Enhancing Programs.NET, C#, Java, Python, etc…MS SQL, MySQL
10Agenda Optimizing the STO System and Data Optimizing the Network for STORemote Access to STOBackup Strategies STOManaging STO day-to-day
11Optimizing STO System Data Optimization Clear STO log periodically Move Transactions to HistoryFun File Doctor to compress data (run at server)Clear STO log periodicallyv9.5 and v9.6 must upgrade to v9.7 to do thisLog can be cleared in v9.7 and higher
12IT Issues that impact STO Antivirus scanningInternet Name ResolutionNetwork CommunicationsServer disk I/OServer RAM Utilization
13Antivirus Necessary Evil, we need antivirus solutions Real-Time scanner of antivirus should be reviewed, default is to scan all filesReal-Time scanner should NOT be set to scan all files.Sage recommends excluding many folders in KB116381Aktion recommends setting antivirus to scan only specific files types that can have a virus, not all files.
14Name Resolution Problems STO uses Internet Name Resolution to find your server.DNS problems can have a performance impact on running STOAll workstations should use the server’s Active Directory integrated DNS server, not public DNS server.
15Network Problems10 Mb network will transfer (Copy / Paste) a files at 1 MB per second.Duplex mismatch issues can seriously degrade the network when the network gets busy.Managed Switches will show CRC Errors or truncated packets in the log.Problems can be address by not using auto settings for duplex on the switch and / or network adapters (typically only done if a problem is found)
17Sources of Disk Problems Fragmentation. Use standard Windows tool to defragment the drive. Run it periodically after hours when no one is on the system.Out of date disk driversPhysical disk problemsOut of date hardware or over utilized system
18Server RAM Utilization 32 bit OS can only address 4 GB RAMMemory Hogs:MS Exchange ServerMS SQL ServerSTO Document Management
19Remote Access Must use remote desktop product like Citrix XenApp ServerMicrosoft Remote Desktop Server (Terminal Server)Other remote desktop products will probably work (LogMeIn, GoToMyPC), but are not supported by Sage.Running STO over a WAN / VPN WAN is NOT supported when STO server is remote from where the STO client is installed on the workstation
20Citrix / RDP Server Tweaks Install as you would any application on a Citrix / Terminal Server (via Install Mode)Set the Pervasive Workgroup.SQL Service to use a domain account that has access to STO dataUse Pervasive Control Center (PCC) to disable Cache under MicroKernal Router.Fixes issues with files left open in PVSW when users are doneWill show proper username of connected users in Pervasive MonitorApply security settings per STO KB244
21Threats to your data Natural disasters Intentional damage Fire, Flood, Tornado, Lightning, etc.Intentional damageMalicious user or hacker deletes, modifies or removes dataUnintentional damageService disruption, system issues, software upgrade / change issues
22Backup RoutinesDaily Full Backup with capacity for multiple restore points over the past several weeks.On the fly backups. STO has a backup tool, but it only backs up data. Need to use 3rd party backup tool to backup everything.Periodic backup for historical purposes (quarter end / year end)
23Ten Tape RotationMon, Tues, Wed, Thu tapes used each of these respective days.Week 1, Week 2, Week 3, Month 1, Month 2, Month 3 used on Friday nights in rotation.W1, W2, W3, M1W1, W2, W3, M2W1, W2, W3, M3
25STO Backup Goals Full Backup every day Multiple Restore Points Off-Site Storage
26Managing STO day to day Upgrades and Updates Locked files in AccountingGhost Users in Estimating License ManagerODBC on 64 bit systems
27STO Upgrades vs. Updates Physical media which will arrive via UPS (CD/DVD)Typically has changes to features / capabilitiesTakes more time to complete and system requirements may changeUpdatesDistributed via a download link in alert from SagePatches / changes for your currently installed (CD) version. Commonly these changes are for Payroll or other tax reporting reasons. There can be updates for other reasons.Quicker to install and typically no system requirement changesFull System Backup before doing Upgrade or UpdatesLaunch full application (not Sage Desktop) and Help -> About to find version.
28STO UpdatesNot all updates apply to all clients. Read the alert to see if the update is worth the effort for your specific installation.Updates are cumulative. Update 3 has all the previous fixes / enhancements included in Update 1 and Update 2.New workstation setup will have NO update.Recommend putting the currently used update in the WININST folder for easy reference in the future.Server and all workstations must use the same update.
29Version ProblemsIf the server is running a different version of the software from the workstation, you will get a TS 6102 Error.Check the version at the server or other workstations to see what version and update they are using.
31Locked Files in Accounting Periodically, exclusive access to data is desiredInstalling upgrades / updatesClosing Month / YearRunning File DoctorRun Pervasive Monitor at the server consoleStart Run W3MONV75Use as tool to gracefully get users out of STO
33Ghost Users in Estimating Occurs with Estimating License Manager on server, not with security device connected to workstations.Have all users exit EstimatingAt the server use Windows Services management tool to restart the Sentinel RMS License Manager service.
34ODBC on 64 Bit Systems x86 = 32 bit x64 = 64 bit Timberline ODBC is 32 bit only. 64 bit systems have both 32 and 64 bit ODBC tools installed. Menu will only show 64 bit versions.Stick with 32 bit MS Office 2010.32 bit ODBC AdministratorStart Run ODBCAD32C:\windows\sysWOW64\odbcad32.exe