Login to participate
Endpoint Management & Virtualization IdeasRSS
2

pcAnywhere Command Queues - Feature Enhancement / Request

theUtmost's picture

Hello

(this is a clone of a pcAnywhere forum post I made earlier. Another member pointed out here was a better place for it...)

I am a long-time pcAw user (since v8. something - I forget exactly) with a couple of queries/suggestions on current functionality within pcAw, specifically around the management of Command Queues.

For the record, I have read all the help available, and searched online but there are few forum topics dealing with this area...

My current version of pcAw is v 12.1.0 build 446 , both at Host and Remote ends, and OS = WinXP Pro 32-bit
Yes, I am aware there is a new version, can anyone confirm whether the following requests for enhancements have been implemented in v12.5 (or newer to extend the "life" of this forum post)?

I would like to see:

1) When adding Remote items to a Command Queue, I should be able to add MULTIPLE existing remotes using Shift-select or CTRL-select methods.
It seems you can only add ONE at a time which is very slow when you have > 130 remotes you want to add to a given Command Queue !!!

2) Connection failures / individual "command per Remote" failures logged to the report
The "Generate Report" option on the Settings tab gives a woefully inadequate report.
The report does NOT even tell me which out of the > 130 Remote clients could not be connected to !! (I know there were some failures to connect because I watched the entire queue run).
This is a fairly major failing of the Command Queues - how can we reliably automate file copies etc if we cannot trap exceptions?

3) Some sort of overall progress / status display of a queue as it is running
Yes, I know the intention is that these Command Queues be run "unattended", but given the apparent issue 2) above I need to watch and try and figure out which ones didn't connect etc.
There is no visible list of which machines have been connected to and which have yet to be attempted which again makes tracking progress or trapping exceptions/failures very difficult.
I'm NOT asking for an accurate "time remaining" progress bar.
I realise that would be nearly impossible due to potential differing connection speeds to all of the remote clients and many other variables.
I'd just like to know:
A) What is the CURRENT Remote being connected to (show the IP address or TAPI entry and Remote.CHF name)
B) What is the NEXT remote in the Queue that will be connected to (IP address and Remote.CHF name)
C) What was the PREVIOUS Remote in the Command Queue that was connected to (IP address, Remote.CHF name and maybe Windows machine name if succesful connection was made)
I'm thinking a fairly simple list, where previous entries are ticked green for succesful, crossed red for failure (full details would be in the log...) current item has a green blinking dot and pending/next entries in the list are grey.
Something like that would work well for me anyway :)

There was a 4) but I can't recall what it was right now...

I'd really love to hear from any Symantec employees on the above, but if any pcAw users out there have any useful tips or would like to put their oar in here you're most welcome!
Cheers,
theUtmost

theUtmost's picture

pcAnywhere v12.5 Command Queues - no improvement...

It's been a month since I put this up and it seems to have garnered... no interest...

I now have v12.5
In the unlikely event that anyone reads this - no the Command Queues have not improved, so my three feature requests as above still stand.

If anyone uses pcAnywhere to deploy software or settings to a large number of machines, I'd love to hear how you're doing it?
Cheers,
theUtmost