If you install Vmware vSphere client on your Windows 7 you get error parsing the server myserver client.xml file. Login will continue,contact SysAdmin

If you install Vmware vSphere client on your Windows 7 you get error parsing the server myserver client.xml file. Login will continue, contact your system administrator.


This happens because vsphere client is not supported under Win7.
Here there is a workaround that’s worked for me:
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a element and a element as shown below. Save the file.


...




3. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=C:\ProgramFiles\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
C:
Cd\”c:\program file\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\”
VpxClient.exe

Jeyo Mobile Extender 2.5 does not work under Windows 7

Jeyo Mobile Extender 2.5 does not work under Windows 7


You still see the “not connected” message even if you have correctly installed the software and your smartphone is connected to your desktop.
This happens because a firewall issue: to resolve the problem open “Windows Firewall with advanced security” control panel and create a new inbound rule.
Choose the Program located under %Program Files% (x86)\Microsoft Office\Office 12\OUTLOOK.EXE
And under Protocol and Ports choose protocol type: TCP, Local Port: Specific Port 9035
Action: Allow the connection
Profile: Uncheck Domain and Public
And choose a custom name to identify the rule in the future.
When you will apply the rule click on send/receive button under your Outlook toolbar and you will fix the problem.

Sharepoint list cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with WSS

Sharepoint list cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls


This problem is because an incompatibility between Office Web Components 2003 and 2007. Maybe you have installed an old version of this feature and during the upgrade process some wrong configuration was not removed (this kind of configuration is usually on HP client machines with OS pre-installed).

To avoid this problem you have to search and delete the following RegKey:

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{65bcbee4-7728-41a0-97be-14e1cae36aae}]

After you removed the regkey above, close and open Internet Explorer.

The problem is fixed!

Cheers.

When trying to run any generic report delivered with Operations Manager reporting I receive: Cannot initialize report. Value cannot be null.

When trying to run any generic report delivered with Operations Manager reporting I receive: Cannot initialize report. Value cannot be null. Parameter name: GroupList
When trying to run any generic report delivered with Operations Manager reporting I receive: Cannot initialize report. Value cannot be null. Parameter name: GroupList

1) Browse to http://localhost/reports
2) Click on details to show all data-sources and choose “properties” of “Data Warehouse Main”.
3) Change the connection string to be: data source=;initial catalog=OperationsManagerDW;Integrated Security=SSPI
4) Uncheck Credentials supplied by the user running the report and check Credentials not required.
5) Click on apply and re-run the report.

The problem will be fixed

HOW TO MIGRATE DPM SRT

HOW TO MIGRATE DPM SRT (Microsoft Data Protection Manager – System Recovery Tool)

1. Stop DPM System Recovery Tool DataStore service
2. Stop MSSQLSERVER$SRT service
3. Disconnect and Reconnect to the new server the iscsi LUN if you have one, otherwise you have to use robocopy.exe (with parameter “/COPYALL”) to copy the source driveletter:\RPStore to the new server maintaining the same directory name.
4. Install DPM SRT on the target server and set the folder RPStore as the backup folder you had previously copied.
5. When the installation is finished, stop the MSSQLSERVER$SRT service.
6. Go to C:\program files\Microsoft SQL Server\MSSQL.1\MSSQL\Data and rename the following files:
DPMSRT.mdf
DPMSRT_log.ldf
RMFileStore.mdf
RMFileStore_log.ldf
7. Copy the following files from the source server to the target server:
pub.key *.rsd \Tasks\*.* %windir%\Tasks\*.job
8. Move all the files sorted on point 6 from the new server to another folder of the new server (or take a backup of the 2 databases if you want)
9. Copy all the files sorted on point 6 from the old server to the new server
10. On the new server start SQL Server 2005 Surface Area Configuration à Surface Area Configuration for Services and Connections à Remote Connections then choose “Use TCP/IP only”
11. Start SQL Server Browse Service and MSSQLSERVER$DPMSRT services on the new server and connect the instance named newserver\dpmsrt to a valid SQL Management Studio and execute this command:
Use DPMSRT
Update dbo.FilestoreTable
Set Name = --insert here the netbios name of the new server
Set ComputerName = --insert here the FQDN of the new server
Set RepositoryPath = --insert here the repository path of the new server
12. Set the correct password on all scheduled tasks of Windows and on the DPM Recovery Schedule Console
13. Reboot the new server and check if all of the services are running and if the DPM SRT is working correctly trying to submit a job for test purpose
Enjoy :-)