Detecting MSXML4, MSXML6 Versions

Issue:
Service Pack of MSXML is not apparent. For example, the Add\Remove Programs applet may list MSXML6 Parser as an installed program, without mention that it is Service Pack 2.
Environment:
Windows All Versions
Solution:
Look at the version of the %systemfiles%\msxml*.dll
The number which follows the major version is the "Service Pack"
For example, if on the properties of msxml6.dll, the version is 6.2, then the Service Pack is 2.

Project: Detect MSXML Service Pack from Command Line
Obtain the latest version of "filever.exe", available for free from Microsoft as part of the Windows Support Tools. For example, from http://www.microsoft.com/en-us/download/details.aspx?id=18546
Then, run the following:

filever.exe C:\Windows\System32\msxml* > xmlversions.txt
findstr /C:"  4.0" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4)
findstr /C:"  4.1" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP1)
findstr /C:"  4.2" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP2)
findstr /C:"  4.3" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP3)
findstr /C:"  6.0" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6)
findstr /C:"  6.1" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP1)
findstr /C:"  6.2" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP2)
findstr /C:"  6.3" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP3)

Symantec Endpoint Protection Client Rolls Back During Installation

Issue:
Symantec Endpoint Protection Client Rolls Back During Installation
Environment:
Windows client (XP) in need of an Endpoint Protection Client in a domain with Symantec Endpoint Protection Server and other working Symantec Clients
Symptoms:
Product initially appears to be installing fine. Near the end of installation, the progress bar rolls back and the installation fails.
Solution:
I've encountered this issue a few times... Try the following in order of most to least likely:
1. Verify you are logged in as Administrator
2. If user permissions are misconfigured, try using a different Administrator account to perform the installation. For example, use the local system administrator account, or a newly created administrator account, or your backup administrator account. If this fixes your issue, you should track down why your administrator account is limited where your other accounts are not.
3. Perform a cleanup of Symantec Applications on the client:
A. Run Cleanwipe (Symantec's Installation Cleanup tool), Reboot, then try reinstalling. Select "yes" to each Cleanwipe option (Skip if cleanwipe not available)
B. Verify in Add\Remove Programs that both Liveupdate and the Client are removed.
C. Use a registry analyzer to clean Symantec References (ccleaner, for example)
D. Reboot, then reinstall the client
4. Verify that the latest root certs are on the system (obtaining from Microsoft is OK)
5. Use the Symantec Support Tool (available from the Server installation media) and run on target machine. Address any issues which this tool finds.
The following steps have not worked for me, but have come up in my research:
6. Install the latest version of Windows Installer
7. Install Liveupdate (LUSETUP.exe) before installing the client on target machine.
8. In the registry (Obligatory Warning: Backup registry before modifying it!),
Find:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData
value=%APPDATA%
and change it to value=%USERPROFILE%\AppData\Roaming
9. Update Internet Explorer 6 to Internet Explorer 7
10. Perform a thorough registry check for Symantec, and be sure to remove:
HKEY_USERS\.DEFAULT\Software\Symantec [remove]
HKEY_CURRENT_USER \Software\Symantec
11. On the server, rebuild the client package and redeploy or re-run on target system
12. Verify that the correct version of the client is being installed (32bit, 64bit, etc.)
13. Click on Start, Select Run, Type: "dcomcnfg", Expand the Component Services, Expand Computers, Expand My Computer, Expand DCOM Config, Right-click LuComServer and select Properties, Click on Identity tab, Select the "This user" option and choose a Local Administrator account., Click OK, Restart the computer

Login Banner for Redhat 6 (RHEL6) Issues

Issue:
Problems occur after lengthy log-in banner is added
Environment:
Redhat 6 with Gnome Login Environment
Solution:
First, let's enable the banner:

gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory/ --type boolean --set /apps/gdm/simple-greeter/banner_message_enable 1

Second, let's add the banner's full text (no returns):
gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory/ --type string --set /apps/gdm/simple-greeter/banner_message_text "YOURBANNERHERE"

Problem 1: No return lines 
First, navigate to the file which contains the banner, %gconf.xml
cd /etc/gconf/gconf.xml.mandatory/apps/gdm/simple-greeter/

Second, modify the file. Locate the banner text and add returns as needed.

Problems 2 and 3: Centered text. Part of the user list is cut off!
First, navigate to the login banner configuration file
cd /usr/share/gdm
Second, backup this file, as modifying it can be very dangerous!
cp gdm-greeter-login-window.ui gdm-greeter-login-window.ui.bak
Third, locate the "auth-banner-label" section in this file and modify/add code in red:

<object class="GtkLabel" id="auth-banner-label">
   <property name="visible">True</property>
   <property name="justify">left</property>
   <property name="wrap">True</property>
</object>
   <packing>
      <property name="expand">False</property>
      <property name="fill">False</property>
      <property name="position">3</property>
   </packing>

CMS Plug-in

Issue:
CMS Plug-in : A supported CMS Plug-in has NOT been installed. CMS will not start until you download the CMS Plug-in on your PC. Click below to download the Plug-in:
Then, you click on the Download button, and get a 404 Error...
Environment:
Accessing an older Cisco 2970 Series switch's website
Solution:
Just ignore the link. All of the features that CMS can do have been rolled into a newer product called Cisco Network Assistant. Download and Run CNA from Cisco's website instead to connect.

Error Copying File: Cannot Copy The specified network name is no longer available

Issue:
Error Copying File: Cannot Copy "filename" The specified network name is no longer available
Environment:
Windows XP client copying to a fileshare in a domain environment
Symptoms:
The failing file was over 1MB. Files under 1MB seemed to copy fine, albeit slowly
Solution:
Replace the faulty switch which was giving my system connectivity to the rest of the network.

Our Linksys SD2008 ver 2.1 switch was to blame. Removal of the cover revealed failed (swelled) capacitors. Apparently, a lot of people have complained about this particular switch, version 2.x. In version 1, there was no problem except for a fan which customers complained was too noisy. Solution? Sell the switch without a fan as version 2 and let it overheat!