Connection issues from Macbook to an view server?

Last days i was running into connection issues with Macbook systems from users.

The solution is short and simple, don't buy Mac use windows.

Above is not the solution ;-), joking no offence against Mac.

You Should install the latest View Client onto your Mac.

Use the link given below to get the latest client:

Go to VMware


If you cannot install the executable from the given link. The security is to tight on your Mac.Change the Gatekeeper settings like below:

64 Bit HP BiDi Channel Component Installer error in eventlog

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 13.05.20010
Time: 10:48:12
User: NT AUTHORITY \ SYSTEM
Computer: TS2003
Description:

  Product: 32/64 Bit HP BiDi Channel Components Installer - The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is the 2753rd

The message had no effect in my case, but it was still a bit annoying. After various test with printer drivers (please note, the HP printer was already over and the error occurred not so far), which beat all wrong, I found the following workaround, which remedied the problem:
 
Workaround:

The MSI packages which will automatically try to install the RDP connection, we need to simply replace it with another (empty) MSI packages.
You can open as the 'Editor' and save the empty file under either the name or hpzbdi32.msi hpzbdi64.msi, depending on whether you need from the 32-bit version or the 64 bit version. Please note that the files are really empty and not coincidentally has a text content, as it may cause other errors. To save the TXT file as MSI packages, you have the editor set the file extension to "All" and the package name followed by '. Msi' state.
Then go to

% WINDOWS% \ system32 \ spool \ drivers \ w32x86

or

% WINDOWS% \ system32 \ spool \ drivers \ x64 \ 3

Directory, depending on your system architecture (32/64 bit), and then locate the file or hpzbdi32.msi hpzbdi64.msi. Rename this file to (eg in hpzbdi32_old) and copy the newly created MSI package to the appropriate folder.
Now when you connect via RDP should autauchen no errors. However, you should see in the log, as our empty MSI package is "installed".
Tags: 32 Bit HP BiDi Channel Components Installer, hpzbdi32.msi, hpzbdi64.msi, Event ID: 10005

Cisco Music on hold file MOH

Goodday all,

Ever wandered why Cisco has some nice MOH file on their voip central??

For people who don't know, it's music while you're on-hold or being transferred.

Youtube:

Click me

Here it is, download it here:

Click me to start downloading

Then upload it to your own phone exchange setup. Voila you're finished ;-)

Help my Exchange server 2010 SP1 logging is oversized

Migrating to Exchange 2010 SP1?

And while migrating the disc is running out of space? That's called Exchange logging.

When you perform an decent backup the logs are flushed.

Use youre inhouse backup solution or just setup Windows Backup. Let it run just one time and all is settled.

TerminalServices-Licensing 4105 – The Terminal Services license server cannot update the license attributes for user “

If you followed my story that i've been upgrading the domain from 2003 to 2008 R2. You also may have noticed that we're using Terminal Servers.

The issue with this at the moment is the following: In the event viewer we got the message that user are logging in with an temp call. Because the Terminal server wasn't an member of the "Terminal Servers License Servers"

Read on, if you have the same issue. Below how to apply the fix. the most easiest way to proceed is described below. The more advanced is kept away, but you can find it here if you like:

http://support.microsoft.com/kb/2030310

Read with caution before clicking "Next" or any other feature just do as described. Nothing more, nothing less.


Use the Delegate Control Wizard to add the permissions to add read\write permissions to the terminalServer attribute or to the Terminal Server License Server attribute of the “user object” by the Terminal Server License Servers group. To do this, follow these steps:

1. Right-click the domain in Active Directory Users and Computers, and then click Delegate Control.
2. In the Users and Groups dialog box, click Add. Type Terminal Server License Servers, and then click OK. In the Users and Groups dialog box, click Next.
3. In the Tasks to Delegate dialog box, click Create a custom task to delegate, and then click Next.
4. In the Active Directory Object Type dialog box, click Only the following objects in the folder. In the list, click User objects (the last entry that is in the list), and then click Next.
5. Do one of the following, according to the operating system that the domain controller is running:
   • For forests that are running Windows Server 2008 or newer Schema:
     
     In the Permissions dialog box, make sure that only the General check box is selected. In the Permissions list, click to select the Read and Write Terminal Server license server check box, and then click Next.
6. In the Completing the Delegation of Control Wizard dialog box, click Finish.