A little something about everything

Install Xrdp on CentOS 5.4

• yum install make.x86_64
• yum install gcc.x86_64
• yum install pam-devel.x86_64
• yum install openssl-devel.x86_64
• Download Xrdp
  • xrdp-0.4.1
• Install Xrdp
  • go to /xrdp directory in terminal
  • make
  • make install
• Start Service
  • cd /usr/local/xrdp
  • ./xrdp_control.sh start

Install the old version of Microsoft RDP on a windows XP system or just search and copy from any pre SP3 windows xp install these two files and place them in a folder.

• mstsc.exe
• mstscax.dll

launch mstsc.exe and connect to your Xrdp server.

There seems to be a problem when installing SQL server 2008 on a windows 2008 RC2 platform.  Generally it will get stuck, hangs at "Install_sql_is_Cpu65_Action:Write_NativeImage_64" or another place about 3/4 the way through the install process. In some cases this may be a permissions issue and others media read/write issue.

Best solution for this is to copy the entire contents of the install media directly to the HDD and run the installer directly from the hard drive as the administrator directly from console and not from RDP. This seems to solve the problem in all cases so far.

Error:

Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.

Issue,

The certificate is still being processed and has not yet been added to the server.

Resolution

Click ok and wait

After waiting refresh (F5) the certificate window within IIS.

You will notice that the SSL certificate is missing a friendly name, in order to fix this you can do the following.

Start > RUN > type in mmc and click enter

Click File Add/Remove snap-in

Double Click Certificates > Computer account then next, Local computer then Finish, OK

Browse to Personal > Cerfificates then right click the new certificate and click properties, Enter a Friendly Name and click OK.

You can close all windows now.

This works but you should still stop and backup your ts3 server.

After you backup is complete follow these steps.

While ts3 server is stopped start the server using this command: (assuming you are running 64 bit server on windows)

(Drive):\Path\ts3server_win64.exe serveradmin_password=YourNewPassWord

(You can do this by making a shortcut and editing the target location as well)

Now you have an updated TS3 admin password, with this you can create a new privileged key.

Using puttytel.exe or any other telnet client to type the following commands:

telnet localhost 10011 login client_login_name=serveradmin client_login_password=YourNewPassWord use sid=1 tokenadd tokentype=0 tokenid1=6 tokenid2=0

(localhost if your server is hosted on the pc/server you are running telnet on, otherwise just use the ip or server name)

After the last command the server will respond with a token=YourNumbersAndLettersToeknID

Copy this and past it into your TS3 client under permissions > use privileged key.

In order to fix this bug you can simply run this command on the effected database after you have used the backup (sql2000) / restore sql2005/2008) or detach attach methods.

command to run:

 exec sp_change_users_login'Update_One','dbusername','dbusername'

Replace "dbusername" with the problem user account. both should be the same.

This will remove the ghost user from the sql 2000 server and replace it with the new user on your sql 2005 / 2008 server. Be sure to have the user created before running this command.

Errors associated with this are as follows:

"login name must be specified Database user"

"The database principal owns a schema in the database, and cannot be dropped"

"user group or role already exists in the current database"

"can't delete sql user in database"