The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
ezki
6 years agoNew Contributor
LMI Central Remote CMD totally broken
The first image is the normal functioning remote cmd , after updating LMI client we get some useless Powershell terminal that has no copy paste abilities and all the features such as the obviously CRITICAL remote Clipboard is missing!!!!
I do not have one to many features in my LMI and rely on the 121 CMD .
Why is this broken and how can I get the perfectly good, working CMD back???????
Note I have tried reboots, reinstalls. Nothing works, I cannot get my old CMD back
Why have you ruined a perfectly good feature????????? :smileymad:
7 Replies
- ezki4 years agoNew Contributor
How did LMI go from being one of the best, most intuitive MSP RC tools to this total **bleep** show!
- Horrific mem leak issues that make software almost unusable.
- Very slow refresh / login on ignition client
- Very long RC time out when you switch to session 0 user , ie. desktop to windows login
- CMD CopyPaste totally bust
I concur, the CMD is still broken, what a disaster!
Also, a new issue, sometimes the CMD tool wont even load at all until a LMI service restart!
- MWPollard4 years agoActive Contributor
It's been an additional year and a quarter, and this key feature - which you said was coming "soon" - seems to still be missing.
- navid19704 years agoNew Contributor
in Oct, you posted you would have an ETA soon . . it's still broken. Cripples us really.
- AshC6 years agoRetired GoTo Contributor
oska I apologize for the difficulty, and will have an ETA on delivery soon.
- oska6 years agoNew Member
Hi,
How can we copy and paste into the new remote powershell? I cannot do any admin work remotely on the background, you said the fixed will be coming out next release what is the EST for that?
- AshC6 years agoRetired GoTo Contributor
We've found the problem with the LMI update and have a fix coming in a future version. Thanks for your patience while we finalize testing.
- PeterTGIT6 years agoActive Contributor
Same issue. Don't know how this hasn't been resolved yet.