Introduction This article describes how to transfer the logins and the passwords between instances of Microsoft SQL Server 2005, and Microsoft SQL Server 2008, on different servers. For more information about how to transfer the logins and the passwords between instances of other versions of SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: 246133 (http://support.microsoft.com/kb/246133/ ) How to transfer logins and passwords between instances of SQL Server Original Article can be found here More Information In this article, server A and server B are different servers. Additionally, both server A and server B are running SQL Server 2005. Note This information also applies to SQL Server 2008. After you move a database from the instance of SQL Server on server A to the instance of SQL Server on server B, the users may not be able to log in to the database […]

Summary ePolicy Orchestrator (ePO) 4.0 setup is based on the Microsoft Windows Installer technology. When you attempt to install ePO 4.0, any failure during setup will cause the installer to roll back the changes. In some rare instances, the rollback might not occur successfully and your ePO installation may be left in an incomplete state. This can also happen when a Patch installation has failed. In such scenarios, you may want to reinstall ePO and restore the ePO 4.0 database. The following are manual removal instructions for ePO 4.0 if you are unable to remove ePO using the Windows Add or Remove Programs feature. Problem ePO 4.0 uninstallation fails from Add or Remove Programs. Solution These steps require the Microsoft MSIZap utility. This may already be present on the server from previous MSI-based installations, but if not it is part of the Microsoft Windows Install Clean Up Utility. After installation […]

Useful tip to find the EPO database settings. https://localhost:8443/core/config for the database settings.

Details: All Backup Exec ™ services on the media server run in the context of a user account configured for Backup Exec system services. This account can be created during the Backup Exec installation, or an existing user account can be used. To create a service account for Backup Exec during installation, supply a user name and password when prompted. If this computer is in a domain, enter a Domain Administrators account, or an equivalent account that is part of the Domain Admins group. In the Domain list, select or enter the Domain name. If this computer is in a workgroup, enter an Administrators account, or an equivalent account that is part of the Administrators group on the computer. In the Domain list, select or enter the computer name. The account designated for Backup Exec services – whether it is a new account or an existing user account – will […]

This tutorial explains how you can replace password-based SSH authentication with key-based authentication which is more secure because only the people that own the key can log in. In this example, we’re using PuTTY as our SSH client on a Windows system. 1. Get the zip file with all PuTTY binaries http://the.earth.li/~sgtatham/putty/latest/x86/putty.zip 2. Generate a private and public key pair Open PuTTYgen.exe, press Generate button, move mouse. Once the keys are generated, type yourkey passphrase (choose a "hard to guess" one). Save Public key. Save Private key. 3. Configure your Linux server (create user, save public key) For this guide let’s assume you regular login name is autotimesheet (replace it with one that you use regularly). As root, on the shell, type: adduser autotimesheet –disabled-password You will be asked to fill in some details such as the user’s real name (empty string is fine). Now type: su autotimesheet cd /home/autotimesheet […]

Here’s a nice little utility that compresses the SQL backup files .bak using Gzip. The backups will then take up a lot less disk space. forfiles /P G:\SQLBackup\db /S /M *.bak /c “cmd /c if @isdir==FALSE C:\GZip\bin\gzip.exe @path” Add that as a SQL Agent job and call it after the database backup in the maintenance plan.

Migrating SQL databases if during the initial Citrix installation the default database was selected and you want to change it from Master to something else, here are the steps that should be taken: SQL Server: Create a Citrix database called CTX, create a SQL user called citrix and grant the user dbo database access. First Citrix Server: 1. From a command prompt cdprogram filescitrixindependent management architecture 2. copy mf20.dsn mast.dsn Contents of mast.dsn: ODBC DRIVER=SQL Server UID=sa DATABASE=master WSID=CTXSERVERNAME APP=Citrix IMA SERVER=SQLSERVERNAME Description=Citrix This assumes the sa SQL account was used to connect to the database. If DATABASE isn’t a part of this configuration then Citrix knows to default to master. WSID=Name of the server SERVER=Name of SQL server 3. edit mf20.dsn Contents of mf20.dsn: ODBC DRIVER=SQL Server UID=citrix DATABASE=ctx WSID=CTXSERVERNAME APP=Citrix IMA SERVER=SQLSERVERNAME Description=Citrix 4. dsmaint config /user:sa /pwd:sapassword /dsn:"c:program filescitrixindependent management architecturemast.dsn" This tells Citrix what DSN to […]