This would be expected. A large transaction log would cause database mirror problems. Regular backups and truncation should be performed to the Simplify database transaction log to maintain a small size.

Microsoft KB Article - How to stop the transaction log of a SQL Server database from growing unexpectedly - http://support.microsoft.com/kb/873235

The database backup should be performed daily, possibly more often depending on the rate that the transaction log grows.

This problem is related to authentication. With Windows Authentication, the users' permissions are used to gain access to the Simplify database. This works for the primary domain because when the Simplify database is generated, NT Authority\Authenticated Users are granted 'Connect' and 'Read' access to the Simplify database. NT Authority\Authenticated Users does not work for trusted domains, unless the trusted domain resides in the same forest as the primary domain. This can be resolved by switching to SQL Authentication or granted Domain Users from the trusted domain access to the Simplify database.

The Simplify database transactio log is not controlled by the Simplify Suite, rather by the SQL Server. However, these problems can be resolved by follow these steps:

SQL 2005 and 2008

1. Open the Microsoft SQL Server Management Studio application.
2. Right-click the Simplify database and select Properties
3. Open the Options page
4. In the middle you will see Recovery Model, change it to Simple and click OK.
5. Try Shrinking the database from the Microsoft SQL Server Management Studio. Right-click the Simplify database, select Tasks, select Shrink. Execute the Shrink function.

SQL 2000

1. Open the Enterprise Manager application for SQL 2000.
2. Right-click the Simplify database and select Properties
3. Open the Options page.
4. In the middle you will see Recovery Model, change it to Simple and click OK.
5. Try Shrinking the database from the Enterprise Manager. Right-click the Simplify database, select Taks, select Shrink. Execute the Shrink function.

http://www.tricerat.com/support/Simplify%20Suite/What_should_I_do_when....
 

http://www.tricerat.com/support/Simplify%20Suite/How_do_I_save_my_changes.html

http://www.tricerat.com/support/Simplify%20Suite/Where_is_the_Active_Directory_structure.html

http://www.tricerat.com/support/Simplify%20Suite/How_do_I_refresh_the_Active_Directory_in_the_Simplify_Console.html

http://www.tricerat.com/support/Simplify%20Suite/Configure_the_Authorization_Manager.html

http://www.tricerat.com/support/Simplify%20Suite/How_do_I_block_users_from_accessing_Simplify_Console.html

http://www.tricerat.com/support/Simplify%20Suite/What_is_the_Simplify_Console.html

http://www.tricerat.com/support/Simplify%20Suite/Install_fails_with_an_Error_Code_1722.html

http://www.tricerat.com/support/Simplify%20Suite/Cannot_connect_to_the_database_message_during_installation..html

The Simplify Suite can be installed on the follow Windows operating systems:

• Windows 2008*
• Windows 2003
• Windows 2000
• Windows Vista*
• Windows XP*
• Windows 2000 Workstation*
• Windows 7* **

The Simplify Suite requires a Microsoft SQL database.

For additional System Requires click here.

* Simplify Suite v5 added support for Windows 2008, Vista, XP, and 2000. Simplify Suite v4 only installs on Windows 2003, 2000, NT.
** Simplify Suite installs on Windows 7, but triCerat does not actively support installations of Simplify Suite on Windows 7 at this time. Simplify Suite will be fully approved for Windows 7 with the official release.

Although it may not be required, triCerat always recommends an uninstall of Simplify Suite before upgrading.

There are more steps that are recommended during the upgrade. For additional information about this process click here.

The Simplify Suite can be uninstalled with Add or Remove Programs, but follow these directions to ensure that Simplify Suite is removed fully.

The database is a separate entity of the Simplify Suite, therefore uninstalling Simplify Suite will not affect the Simplify database. For more information click here.

Simplify Suite is installed using the Simplify Suite installer. Walk-through directions are available here.

Please review the Pre-Installation Checklist.

The recommended upgrade steps for Simplify Suite are:

1. Uninstall Simplify Suite
2. Restart Server
3. Install new Simplify Suite

In the event you cannot restart the server follow these steps:

1. Uninstall Simplify Suite
2. For 32-bit, in C:\Windows\System32\Spool\Drivers\w32x86\3 delete sd4ui.dll and sd4drv.dll. For 64-bit, in C:\Windows\System32\Spool\Drivers\x64\3 delete sd4ui.dll and sd4drv.dll. If these files cannot be deleted then rename them (for example rename sd4ui.dll to sd4ui.old).
3. Install Simplify Suite

These steps are instrumental for Simplify Printing. Without following the correct directions, the ScrewDrivers driver may not patch. Printers will not create if the driver does not upgrade. Always test after upgrading Simplify Suite.
 

The Simplify Suite must be installed at the console of the terminal
server (i.e. session 0), not through a remote session.  There
are a number of ways to access the console:

- If it is Windows Server
2003, use the remote console switch.  If
you are unfamiliar with this option, please   
refer to the following Knowledge Base (KB) article from Microsoft (278845).

- Use a third-party utility
such as VNC or Dameware

- Use a remote KVM switch

Unfortunately not at this time, but a triCerat support rep can help make migration go smoothly. Learn more by contacting triCerat support.

The database is a separate install from the Simplify Suite, so uninstalling or upgrading the Suite will not affect the install of the database. This is true even with the MSDE bundle provided by triCerat, which first installs the MSDE and then installs the Simplify Suite. In this scenario, the MSDE and it’s databases remain on the system even if the Simplify Suite is removed.

The Simplify Suite install is in windows installer format, allowing
for silent installations and deployment through Active Directory. Silent
install is initialized using the /q switch with msiexec.exe, and then
passing in values for properties. The command line syntax to set a property
is PROPERTY=VALUE. Valid properties include:

INSTALLDIR
SQLSERVERNAME
SQLTRUSTED
SQLUSERNAME
SQLPASSWORD

Below is an example of correct syntax to begin a silent installation
of Simplify Suite.

msiexec /i simplify.msi /q SQLSERVERNAME=SQLSVR SQLTRUSTED=no SQLUSERNAME=sa
SQLPASSWORD=sapwd

SQLUSERNAME and SQLPASSWORD are only necessary when SQLTRUSTED=no. If
SQLTRUSTED=yes, then the install ignores the SQL username and password.

A silent installation cannot be performed using the install bundled
with the MSDE (SimplifyMSDE.exe). Instead, the (Simplify.msi) will is
required. Additionally, a silent install cannot perform database operations
such as creating a new database. A simplify database must already exist
for the silent install to work.

The install will prompt for a reboot if one is required. The server does need to be rebooted after uninstalling the product.

Yes, during the install an option is presented to choose which features
to install. At this selection dialog, choose to install the management
console, and disable other options by selecting 'Entire feature will
be unavailable' for 'Products'.

No, ScrewDrivers does not work with PCoIP. However, VMware View using RDP instead of PCoIP is compatible with ScrewDrivers.

The support of PCoIP currently in development.

Different ScrewDrivers Client packages install different files, so follow the appropriate directions. If you are receiving an error in Add/Remove Programs that prevents the ScrewDrivers Client uninstall then you must use Microsoft's Windows Installer Clean Up Utility to remove MSI instance of ScrewDrivers.

ScrewDrivers RDP Only

• Delete Program Files\triCerat\
• Delete sdrdp5.dll from Windows\System32\
• Delete sd4client.cpl, sdcpl.exe, or sdclient.cpl from Windows\System32. Note that the the client Control Panel applet filename has changed with various revisions of ScrewDrivers v4.

ScrewDrivers Client v4 (with RDP and ICA)

• Delete Program Files\triCerat\
• Delete sdrdp5.dll from Windows\System32\
• Delete sd4client.cpl, sdcpl.exe, or sdclient.cpl from Windows\System32. Note that the the client Control Panel applet filename has changed with various revisions of ScrewDrivers v4.
• Delete sdica6.dll from the Citrix ICA Client directory, usually Program Files\Citrix\ICA Client

ScrewDrivers ICA Only

• Delete Program Files\triCerat\
• Delete sd4client.cpl, sdcpl.exe, or sdclient.cpl from Windows\System32. Note that the the client Control Panel applet filename has changed with various revisions of ScrewDrivers v4.
• Delete sdica6.dll from the Citrix ICA Client directory, usually Program Files\Citrix\ICA Client

There are different ways to deploy ScrewDrivers using the Citrix Web Interface, but the simplest way is embedding the ScrewDrivers CAB install into the Citrix Web Interface.

On the Citrix Web Interface server(s), edit the layout.inc file in C:\inetpub\wwwroot\Citrix\XenApp\app_data\include.

Place the ActiveX code below the <html> and <head> portion. Here is sample ActiveX code:

<OBJECT ID="Screwdrivers v4 Client" CLASSID="clsid:050A3800-6C03-48a5-A6D7-14CCF18A700D"
CODEBASE="v4full.cab#version=-1,-1,-1,-1"></OBJECT>

You also need to place the ScrewDrivers CAB, in this example v4full.cab, into C:\inetpub\wwwroot\Citrix\XenApp\auth.

You must modify the web interface to allow ScrewDrivers to work with Remote Desktop via the web interface. Without these modifications ScrewDrivers is unable to create a virtual channel within the Remote Desktop Protocol. Please follow the appropriate directions:

Windows Server 2003

1. Edit the web portal's html file, typically default.htm in C:\inetpub\wwwroot\tsweb\default.htm. Check Internet Information Service (IIS) if you do not know where the Remote Desktop html file resides.
2. In the html file find "Device redirection options". It should read as:

'Device redirection options

MsRdpClient.AdvancedSettings2.RedirectDrives = FALSE

MsRdpClient.AdvancedSettings2.RedirectPrinters = TRUE

MsRdpClient.AdvancedSettings2.RedirectPorts = FALSE

MsRdpClient.AdvancedSettings2.RedirectSmartCards = FALSE

* the TRUE or FALSE values may differ in your environment

3.  Add the following line of code at the end of the "Device redirection options" section:

MsRdpClient.AdvancedSettings.PluginDlls = "sdrdp5.dll"

After you finish, the "Device redirection options" should read as:

'Device redirection options

MsRdpClient.AdvancedSettings2.RedirectDrives = FALSE

MsRdpClient.AdvancedSettings2.RedirectPrinters = TRUE

MsRdpClient.AdvancedSettings2.RedirectPorts = FALSE

MsRdpClient.AdvancedSettings2.RedirectSmartCards = FALSE

MsRdpClient.AdvancedSettings.PluginDlls = "sdrdp5.dll"

4. Save this file and restart the Internet Information Services service.

Windows Server 2008

1. Open up the "web.config" file in the TS web directory, typically C:\Windows\web\ts\web.config on your server.

2. Look for these entries:

<add key = "xPrinterRedirection" value = "true" />
<add key = "xClipboard" value = "true" />
<add key = "xDriveRedirection" value = "false" />
<add key = "xPnPRedirection" value = "false" />
<add key = "xPortRedirection" value = "false" />

Add the following:

<add key = "xPluginDlls" value = "sdrdp5.dll" />

3. Restart IIS

These steps are recommended when ScrewDrivers Server cannot be removed with Add or Remove Programs. Do not remove ScrewDrivers while in production. Only remove ScrewDrivers after the users Log Off the server. A restart is generally recommended after completing these steps.

Windows XP, 2000, 2003 x86

1. Delete the following files and directories, and rename any files that cannot be deleted:
   • Program Files\triCerat
   • system32\spool\drivers\w32x86\sd4drv.dll
   • system32\spool\drivers\w32x86\sd4ui.dll
   • system32\spool\drivers\w32x86\3\sd4drv.dll
   • system32\spool\drivers\w32x86\3\sd4ui.dll
   • system32\sd4notify.dll
   • system32\sd4ICA6.dll
   • system32\sd4pRDP5.dll
   • system32\sd4pTCP.dll
   • system32\sd4server.cpl and/or sd4servercpl.exe
2. Remove the following regsitry entries
   • HKLM\SOFTWARE\triCerat
   • HKLM\SYSTEM\CurrentControlSet\Control\Printers\Environments\Windows NT x86\Drivers\Version-3\ScrewDrivers4
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PICA6
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PRDP5
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PTCP
   • HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SYSTEM\ControlSet001\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SYSTEM\ControlSet003\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ScrewDrivers Server v4

Windows XP, 2003 x64

1. Delete the following files and directories, and rename any files that cannot be deleted:
   • Program Files\triCerat
   • system32\spool\drivers\x64\sd4drv.dll
   • system32\spool\drivers\x64\sd4ui.dll
   • system32\spool\drivers\x64\3\sd4drv.dll
   • system32\spool\drivers\x64\3\sd4ui.dll
   • system32\sd4notify.dll
   • system32\sd4ICA6.dll
   • system32\sd4pRDP5.dll
   • system32\sd4pTCP.dll
   • system32\sd4server.cpl and/or sd4servercpl.exe
2. Remove the following regsitry entries
   • HKLM\SOFTWARE\triCerat
   • HKLM\SYSTEM\CurrentControlSet\Control\Printers\Environments\Windows NT x86\Drivers\Version-3\ScrewDrivers4
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PICA6
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PRDP5
   • HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors\SD4PTCP
   • HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SYSTEM\ControlSet001\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SYSTEM\ControlSet003\Control\Terminal Server\AddIns\sd4monitor
   • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ScrewDrivers Server v4

Windows Vista/2008 x86 and x64 (additional steps)

1. In services.msc stop the Simplify Notification Service
2. In cmd.exe execute sd delete SimpNtfy
3. Delete C:\Windows\System32\SimpNtfy.exe
4. Complete the steps above for Windows XP/2000/2003

ScrewDrivers is a print driver utility, and must be removed when clients are not connected to the Server. You do not need to use Install Mode because ScrewDrivers is an MSI, and does not cache data during install or uninstalls. Follow these directions to ensure ScrewDrivers is upgraded properly:

1. Connect to the Server at the console. If you are remote use mstsc.exe /console.
2. Verify all remote sessions are closed. Connections can be managed in the Users tab of tsadmin.exe and taskmgr.exe.
3. Verify there are no ScrewDrivers printers on the server. In Printers and Faxes audit the printer 'Model', and delete any printer using ScrewDriver4. If you cannot delete a specific printer then stop the Print Spool service, delete all files from the Print Spool directory, and start the Print Spool service.. The default directory for the Spooling is Windows\System32\Spool\Printers. If you cannot delete all ScrewDrivers printers then you MUST restart the server after uninstalling ScrewDrivers.
4. Access Add or Remove Programs, and remove ScrewDrivers Server v4.
5. Install the new version of ScrewDrivers Server.
6. Test and verify the new version of ScrewDrivers works.

Yes and No.

ScrewDrivers supports custom paper sizes defined on the client-side within the Print Server Properties and the client driver.

ScrewDrivers does not support custom paper sizes defined by applications on the server side.

ScrewDrivers doesn't install anything in the "Start Menu", ScrewDrivers console is accessible via the control panel.

Simplify Profiles is a hybrid profile management utility for Windows designed to provide the same benefits as
roaming profiles
without the management problems. click here.

1. Install the ScrewDrivers v4 Print Server Agent on each node of the print cluster
2. On one node go to Start > Programs > Tricerat > ScrewDrivers v4 Print Server Agent and open the ScrewDrivers Console.
3. Select Tools > Cluster Configuration
4. Note that this step will restart the clustered Print Spool service. If the nodes are part of a pre-existing Windows print cluster, all the necessary cluster information should be automatically filled in, and the setup is complete.

If a Windows print cluster is not currently setup, a new cluster will be setup...

- In the Cluster Name tab, the physical Cluster Name should already appear; below it, enter a network name for the ScrewDrivers cluster.

- In the Network Settings tab, select a network connection for the cluster, and enter an unused static IP and subnet mask for the print cluster

- In the Cluster Resources tab, select a shared disk to be used for the cluster's spool directory; you can optionally enter a name for the cluster that will appear under when viewed through Microsoft's cluster administration tool.

5. When connecting to the cluster in the Simplify Console, be sure to use the ScrewDrivers Print Cluster name and not the physical cluster or node name(s).

This error occurs if the Simplify Console cannot handle the printer data from the Print Server. To save time and resources, the printer data is cached on the Print Server. In v5.3.00 a new printer data standard was introduced. After upgrading, the cached printer data on the Print Server are no longer valid, and must be manaully cleared.

On the Print Server, delete HKLM\Software\triCerat\Simplify Printing\Printers, then retry the Import New Printers or Refresh All Printers function in the Simplify Console.

If this does not fix the problem, then very the sdservice.exe on the Print Server and Simplify Console are identical. sdservice.exe is found in C:\Program Files\triCerat\Simplify Printing\ScrewDrivers Print Server v4.

If this problem persists after synchronizing the sdservice.exe versions, then contact support@tricerat.com.

Yes, Simplify Printing works with Windows Print Clusters, but there are additional configuration steps. Follow these directions:

1. Install the ScrewDrivers v4 Print SErver Agent on each node of the print cluster.
2. On one node go to Start > All Programs > triCerat > ScrewDrivers v4 Print Server Agent, and open the ScrewDrivers Console
3. Select Tools > Cluster Configuration
4. Check the option "Enable ScrewDrivers Print Server Clustering" and give a name to the ScrewDrivers print Cluster. All other fields should be auto filled with the appropriate information.
5. Create a Print Server object in the Simplify Console and Import the printers. Use the ScrewDrivers Print Cluster name and not the Print Cluster name from Active Directory.

This generic Windows error appears when print driver DLLs are the incorrect version or missing.

It is recommended to perform a clean installation of Simplify Printing when encountering this error. The steps to be taken are:
1. Uninstall Simplify Printing
2. Reboot
3. Re-install Simplify Printing

Specifically, these files must be removed and replaced:
- Windows\System32\Spool\Drivers\w32x86\3\sd4drv.dll*
- Windows\System32\Spool\Drivers\w32x86\3\sd4ui.dll*
- Windows\System32\SQLAPI_Mtu.dll

* For Windows x64 systems, use Windows\System32\Spool\Drivers\x64\3\

Please refer to the following help document. http://www.tricerat.com/pdf/SimplifyPrintingPrintServerAgent.pdf

Version 1.0

• Windows 2000 install fails (see triCerat support for manual installation instructions while we work on a fix)