Anith Gopal

Hallo zusammen, Folgendes Szenario: Der Kunde nutzt in seinem ganzen Unternehmen App-V 4.6 auf den Windows 7 x64 Fat Clients und auch auf den Windows 7 x64 Notebooks. Nun kommt es vor, dass nur auf den Notebooks verschiedene Anwendungen melden sie seien nicht korrekt installiert und es fehlen DLL Dateien. Wie hier zu sehen: Wenn man sich von so einem Start einen Procmon Trace erstellen lässt, dann sieht man folgendes: An diesem Pfad (in diesem Fall V:SAPR3GUI.720SAPguisapshlib.dll) ist diese DLL…( read more )

When building a VPC and installing the Outlook client on Windows Server 2008 I have encountered the following error several times: When asked for the installation location for the Outlook client you get an error messge “The path is not of a legal form”.  This is due to a registry key that is left empty by the server installation. To fix this do the following: 1

It’s pretty well known that Teamprise provides a TFS client that allow access to TFS from Mac, Unix (and Windows).  Their client includes Eclpse integration, a stand-alone explorer and a command-line clent.  What’s not well known is that they are currently working on mainframe support as well.  Pretty soon you’ll be able to access TFS from everywhere you do development. I’m really thrilled they are taking this step because I’ve always believed that it’s important that all people in a software development project are able to access the project resources no matter what their role and no matter what platform they are on.  I’m really looking forward to seeing how this evolved.

Hallo zusammen, mit dem Security Bulletin MS09-035 hat Microsoft ein neues Visual C++ Redist. Package veröffentlicht. Somit liegen im Download Center drei Versionen des VC++ Paketes in der 2005er Ausführung: Microsoft Visual C++ 2005 Redistributable Package (x86) http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=32bc1bee-a3f9-4c13-9c99-220b62a191ee Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647…( read more )

  I have come across this scenario several times while troubleshooting the cases where Upgrade process fails with the below error logged in the upgrade.log file:   [AddSearchToLinks] [3.0.77.0] [DEBUG] [6/12/2009 10:11:48 PM]: Executing SQL DDL Script. [SPContentDatabaseSequence] [ERROR] [6/12/2009 10:41:53 PM]: Action 3.0.77.0 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed. [SPContentDatabaseSequence] [ERROR] [6/12/2009 10:41:53 PM]: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding

When using WLK 1.4 runs W2k3 MSCS test for W2k3 x64 cluster, WLK 1.4 only list Phase 1 and Signed Driver Check on x64.   There is a workaround to get MovN and ValdN to show up:                   Before creating a submission please do the following: 1.        In DTM Studio, open Job Explorer and browse to $WD TestsServerWindows Server 2003 SystemsCluster 2

UNISYS vient de renouveller son équipement déployé dans les MTC de Paris et de Munich. C’est donc un nouvel équipement highend pour les projets SQL Server et les projets de Real Time Infrastructure (datacenter dynamique et flexible – IMS ) Le détail de la configuration: 3 cellules ES7600R 12 CPU Intel 7460 hexa core @ 2.66Ghz Pour un total de 72 cores et 384GB RAM Plus d’information:

This week happens to be Ubuntu Developer Week. Since the Fedora Classroom has nothing scheduled, if you want to learn something head on over to the dark Ubuntu side. With all seriousness (woah that’s a word?) the schedule looks pretty good and its free, so go on over.

Im Zuge meiner Arbeit hier in Redmond habe ich mir die RIA-Services mal etwas genauer angeschaut.

The question came up recently about what ports are really needed for AMT in SCCM.  The documentation ( http://technet.microsoft.com/en-us/library/bb632618.aspx ) indicates a list of ports that are used by AMT for various communication that takes place between various AMT components during management.  The documentation is correct but is also potentially confusing.  One thing to understand is that on the client AMT function is  handled in the firmware – the operating system really is secondary.  It’s possible to fully manage a system via AMT even when it is powered down or the OS is failing to load.  Why is this important?  The Windows firewall.  Based on the documentation we provide listing the required ports a natural thought is that these ports need to be opened on the Windows firewall.  This generally isn’t the case but there is one exception and that is on the Out of Band service point (OOBSP).  The OOBSP, an SCCM site system role, listens for incoming hello messages from AMT systems on port 9971, Since this component IS part of the running operating system we do need to have port 9971 opened in the Windows firewall or hello packets will be blocked and out of band provisioning will not work.  So are the ports documented in the link above relevant?  Absolutely.  if there are firewalls in place other than the Windows client firewall between AMT components you do need to ensure the ports listed are opened and accessible.  Hope this clears up any confusion.

With the recent Apple announcement regarding the availability of Mac OS X Snow Leopard (10.6), we want Live Mesh Mac users to be aware the current Live Mesh Mac software is not compatible with the new OS X version (10.6).