Unable to install CCS agent on server with hostname as COM1

I need a solution

I have a Windows 2016 server machine with hostname as COM1. When I tried to install Symantec CCS agent on it, Symantec encountered an error where the folder of COM1 cannot be created.

After searching online, I found that COM1 is one of the reserved device names and cannot be used for the name of file/folder.

One thing i can do to proceed with the installation is to change the hostname of the server to that of non reserved device name. 

Can I check whether anyone have any ideas on how I can proceed without changing the hostname? Thank you.

0

Related:

7021683: What type of cable do I need to make a serial connection between my PC and HP9000 UNIX console?

The type of cable(s) needed to make a serial connection between a PC and an HPUX host depends on the types of ports you are connecting. Depending on the hardware installed on your PC and host, you may have one or more of the following options:

System
Possible Ports
PC
Serial port

USB port

HPUX host
Console serial port

Console USB port

MUX (multiplexer)

Using a combination of cables, any of the PC port types listed above can be connected to any of the host port types noted. Regardless of which two types of ports you will be connecting, somewhere in the cabling you must use either of the following pieces of hardware:

  • An RS-232 null modem cable (also called an RS-232 cross-over cable), with the appropriate terminators.
  • A Null modem adapter somewhere in the cabling between the PC port and host port.

A null modem cable or adapter crosses the transmit data wire (pin 2) and receive data wire (pin 3).

For example, to make a direct serial connection from a PC’s 9-pin serial port to a 9-pin serial port on the HPUX, you will need a 9-pin RS-232 null modem cable (also called an RS-232 cross-over cable).

Or, if you only have a standard (non-null modem) RS-232 modem cable, you must insert a null modem adapter to the end of the standard RS-232 cable (between the cable and either the console serial port on the host or the PC serial port) to reverse the cable’s transmit and receive signals.

Troubleshooting

After connecting your PC and HPUX console using an RS-232 null modem cable or null modem adapter, if you are unable to make a serial connection to the host using Reflection for HP, verify the following.

  • In Reflection, verify that you have selected the correct serial port for your workstation in Connection > Connection Setup.
  • Make sure that the RS-232 cable you are using is a null modem cable. If you are unsure, insert a null modem adapter between the cable and your workstation port, and then try connecting again.

Related:

COM Port Redirection: How to map a client COM port to a server COM port

LPT and COM port settings are configurable via Studio in XenApp / XenDesktop 7.9 or newer. In versions 7.0 through 7.8, these settings were only configurable using the registry. For more information, see Port redirection policies in Citrix Documentation.

Client COM port mapping allows devices attached to the COM ports on the user’s endpoint to be used during virtual sessions. These mappings can be used like any other network mappings.

For each COM port, a driver in the OS assigns a symbolic link name such as COM1, COM2, etc, which is then utilized by the applications to access the port.

While most PCs no longer have built-in serial (COM) ports, the ports are easy to add via USB converters.

Beware that even if a device can attach to the endpoint via USB directly does not mean it can be redirected via Generic USB Redirection. Some USB devices function as virtual COM ports, which applications can access in the same way as physical serial port. The OS can abstract COM ports and treat them like fileshares. Two common protocols for virtual COM are CDC ACM or MCT.

(When connected through RS-485 port Applications might not work at all. Get a RS-485-to-RS232 converter to use it as a COM port)

Applications suited for serial ports often involve sensors, controllers, old check readers, pads, etc.

Some USB virtual COM-port devices use vendor-specific drivers in place of the Windows-provided drivers (usbser.sys).

These drivers allow you to force the virtual COM port of the USB device so that it does not change even if connected to different USB sockets. This might be done from Device Manager / Ports (COM & LPT) / Properties, or from the Application itself, that controls the Device.

User-added image

Warning: Some applications will only recognize the Device (e.g. signature pad) consistently if it is connected to COM1 or COM2 on the client workstation.

Related:

Missing decimal.h in new Streams environment

I just created a new Streams 4.2.1.3 environment on fresh Centos 7 (64bit x86) image. The Streams install passed all the dependency checks but when I attempt to build a simple application I get the error below.

/opt/ibm/InfoSphere_Streams/4.2.1.3/include/SPL/Runtime/Type/Decimal.h:28:19: fatal error: decimal: No such file or directory

I’m convinced that it’s something wrong with the underlying OS configuration rather than the Streams install because using gcc to compile a one line program with the same include also generates the error. However, I would have hoped that something would show up as missing or failed in the dependency checker since whatever configuration or package provides this is apparently required by Streams.

Has anyone else seen this? Or better yet know what a fix might be?

Related:

Re: Data Mover hardware misconfigured

Hello EMC gurus,

I request your help for a difficult situation on a NS702 :

The primary Data Mover has switched on the standby.

The customer activity is operational on the standby data mover (slot 3).

I have checked the hardware configuration, and the Control Station serial ports were incorrectly connected :

Slot 2 connected to S2 should be S1

Slot 3 connected to S3 should be S2

After a complete shutdown, I have corrected that.

But now, I get :

[nasadmin@nas_cs0 ~]$ /nas/sbin/getreason

10 – slot_0 primary control station

14 – slot_2 hardware misconfigured

5 – slot_3 contacted

[nasadmin@nas_cs0 ~]$

Could you give me some guidelines how to check and correct the Slot 2 configuration before to restore on slot 2 ?

Thank you very much for your help.

Best regards.

Raphlou

Related:

Re: Re: Help setting up a CX3-40f

First, make sure you settings on the PC are correct:

I. CONNECTING TO SP USING SERIAL CABLE AND HYPERTERMINAL

First click Start-> Programs-> Accessories > Communications HyperTerminal.

Second enter the name of the connection (your choice), and click OK.

Under connect using select COM1 and click OK.

Connect null modem serial cable from Workstation COM1/COM2 to front serial port on the CLARiiON.

Configure HyperTerminal connection for the CLARiiON using the following settings:

Connect using: COM1 or COM2 and click Apply.

Bits per second: 9600

Data bits: 8

Parity: None

Stop bits: 1

Flow Control: None (verify that Auto detect and ANSI are selected for terminal emulation if an option).

Note: Make sure that you set the following in the image below on your HyperTerminal session from File > Properties > Settings.

HyperTerminal Settings for Serial Connection to SP.PNG.png

Click Transfer > Capture text > Browse to the location and name the file and click Start.

glen

Related:

Why is multithreaded gnu sort slower on ppc-64 than on x86?

I am running the following command:

time sort -r -nk4 -nk5 -S4G –parallel=24 –temporary-directory=/tmp -s /tmp/test.txt > /tmp/out

The /tmp/test.txt file looks like this:
1 10 1 1.0352e-12 1
1 10 2 1.0352e-12 1
1 10 3 1.0352e-12 1
1 100 3 3.04418e-12 2
1 100 4 1.52209e-12 1
1 10000 1 1.73929e-11 2
1 10001 4 8.6971e-12 1
1 10002 4 8.69872e-12 1
1 10003 4 8.69929e-12 1
1 10005 4 8.70158e-12 1

There are 22,553,742 lines in this file.

On x86 this command ran in ~110s. On ppc-64 it took ~250s.

On modifying the -S4G flag to -S5G, the runtimes were:
On x86 this command ran in ~65s. On ppc-64 it took ~125s.

This showed extraordinary sensitivity to this parameter, but ppc-64 is still roughly twice as slow as x86. I was wondering if there was any way to fix this issue.

This is using sort (GNU coreutils) 8.22 on both x86 and ppc-64.

Related: