When installing from the original disc’s of Microsoft SQL, the following error occured:
“An installation package for the product Microsoft SQL Server Native
Client cannot be found. Try the installation again using a valid copy of
the installation package ‘sqlncli.msi’”
To resolve this, use the add/Remove programs to deinstall the existing SQL Server Native Client installation.
After deinstalling this package, run the setup again and the problem is fixed.
Guide for Installing KMS in windows server, and setting up Volume activation for windows 7 and Office 2010:
[wpdm_file id=”24″]
Here is the link to download the TSM client from the IBM site:
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/
When changing a servername, ingres wil not function anymore. Here is a short how-to, for changing the ingres installation to the right servername.
After reboot the DSM SA Data Manager Service takes about 10 minutes to start, during this time cannot login either remote or at the console.
Answer from Dell:
Regardding the Datamanager taking too long to boot, we have found this issue when we install OMSA on a Server that has “SQL Server Integration Services” or Oracle services. Reason for the delay is the race condition which prevents command reaching the storlib. There is a race condition between the SQL integration service and DSM data manager service.
To avoid this a dependency can be created as per the below Microsoft knowledgebase. This will prevent from this condition.
http://support.microsoft.com/kb/193888
Create a dependancÿ:
The name of the service you would enter in the Data dialog box is the exact name of the service as it appears in the registry under the Services key
Dell OMSA LiveCD 6.0.1 provides the following features
• Safe environment to perform diagnostics or data recovery
• Access to disk diagnostics (Dell Online Diagnostics)
• Access to tape diagnostics (xTalk and IBM ITDT)
• DSET tool built into operating system
• Built in FTP and SMB shares to easily transfer files
• Built in telnet, SSH and VNC servers for remote troubleshooting
• Webex support for Dell technical support access
• OMSA 6.0.1 built in for local and remote access
Read the PDF: http://linux.ins.dell.com/files/openmanage-contributions/omsa-601-live/Guide.pdf
Download the iso: http://linux.dell.com/files/openmanage-contributions/?C=M;O=A
To open firewall ports for SEP you need to know the following ports:
| Number | Port Type | Initiated by | Listening Process | Description |
| 80, 8014 | TCP | SEP Clients | svchost.exe (IIS) | Communication between the SEPM manager and SEP clients and Enforcers. (8014 in MR3 and later builds, 80 in older). |
| 443 | TCP | SEP Clients | svchost.exe (IIS) | Optional secured HTTPS communication between a SEPM manager and SEP clients and Enforcers. |
| 1433 | TCP | SEPM manager | sqlservr.exe | Communication between a SEPM manager and a Microsoft SQL Database Server if they reside on separate computers. |
| 1812 | UDP | Enforcer | w3wp.exe | RADIUS communication between a SEPM manager and Enforcers for authenticating unique ID information with the Enforcer. |
| 2638 | TCP | SEPM manager | dbsrv9.exe | Communication between the Embedded Database and the SEPM manager. |
| 8443 | TCP | Remote Java or web console | SemSvc.exe | HTTPS communication between a remote management console and the SEPM manager. All login information and administrative communication takes place using this secure port. |
| 9090 | TCP | Remote web console | SemSvc.exe | Initial HTTP communication between a remote management console and the SEPM manager (to display the login screen only). |
| 8005 | TCP | SEPM manager | SemSvc.exe | The SEPM manager listens on the Tomcat default port. |
| 39999 | UDP | Enforcer |  |
Communication between the SEP Clients and the Enforcer. This is used to authenticate Clients by the Enforcer. |
| 2967 | TCP | SEP Clients | Smc.exe | The Group Update Provider (GUP) proxy functionality of SEP client listens on this port. |
The Symantec Endpoint Protection Manager (SEPM) use two web servers: Internet Information Services (IIS) and Tomcat. IIS uses port 80 (or 8014) and 443 – Tomcat uses port 9090 and 8443. The communication between IIS and Tomcat uses the HTTP protocol. IIS uses port 9090 to talk to Tomcat, Tomcat uses port 80 to talk to IIS.
Client-Server Communication:
For IIS SEP uses HTTP or HTTPS between the clients or Enforcers and the server. For the client server communication it uses port 80 (or 8014) and 443 by default. In addition, the Enforcers use RADIUS to communicate in real-time with the manager console for clients authentication. This is done on UDP port 1812.
Remote Console:
9090 is used by the remote console to download .jar files and display the help pages.
8443 is used by the remote console to communicate with SEPM and the Replication Partners to replicate data.
Client-Enforcer Authentication:
The clients communicate with the Enforcer using a proprietary communication protocol. This communication uses a challenge-response to authenticate the clients. The default port for this is UDP 39,999.
The Symantec Endpoint Recovery Tool is an image that you can burn on a disc, which you can use to scan and remove malware from client computers. You use this tool for the computers that are too infected for Symantec Endpoint Protection to clean effectively.
(http://www.symantec.com/connect/videos/symantec-endpoint-recovery-tool-sert)
You can download the tool from https://fileconnect.symantec.com/ and you need your license number like B1234567891.
Download the tool and get a USB key with at least 512 MB space
1. Using WinRAR or similar, extract the SERT.iso file to the local file system (assume C:\SERT).
2. Open a command prompt with admin rights.
3. Insert the USB stick into the computer.
4. Type the following command to start Diskpart:
diskpart <enter>
5. Type the following command to list the available disks:
list disk <enter>
This command is important. It will show you what number your USB drive is. Failure to select the right disk at this point may result in loss of data from your hard disk. Normally the drive is Disk 1, but you should confirm before proceeding.
6. Type following commands to format the USB stick and prepare it for SERT:
select disk <number> <enter>
clean <enter>
create partition primary <enter>
select partition 1 <enter>
active <enter>
format fs=fat32 <enter>
assign <enter>
exit <enter>
7. At the command prompt, type the following to copy the SERT files to the USB Stick:
xcopy C:\SERT\*.* <removable disk drive letter>\ /e /h /f <enter>
For updated definition files, download the JDB files and unzip them to the USB key. The JDB files can be found at http://www.symantec.com/business/security_response/definitions/download/detail.jsp?gid=savce
To see how the SERT tool can be updated with the downloaded JDB file, read the following article: http://www.bvanleeuwen.nl/faq/?p=748
Telnet Client allows a computer to connect to a remote Telnet server and run applications on that server. Once logged on, a user is given a command prompt that can be used as if it had been opened locally on the Telnet server’s console. Commands that you type at the Telnet client command prompt are sent to the Telnet Server and executed there, as though you were locally logged on to a command prompt session at the server. Output from the commands that you run are sent back to the Telnet client where they are displayed for you to view.
When you first try to run a telnet command, Windows will informs you that telnet is not recognized as a command
To enable Telnet on Windows Server 2008 follow these steps :
As you can see, Telnet is now recognized by Windows Server 2008 and you can start using it to connect to your telnet servers.
Obtaining a license key for Mail Synchronization:
Downloading the Synchronization Tool for Mail Synchronization:
Installing the Synchronization Tool
