meta user
network profile
| bio | website | neolisk.com |
|---|---|---|
| location | Mississauga, Canada | |
| age | 24 | |
| visits | member for | 9 months |
| seen | Apr 3 at 13:38 | |
| stats | profile views | 4 |
|
Apr 3 |
comment |
RDP suggesting a user name when connecting to a server Cleared both - did not work. Restarted - did not work. It appears my problem is elsewhere. Thanks for your feedback though. +1 |
|
Nov 8 |
comment |
RDP suggesting a user name when connecting to a server @joeqwerty: To talk in business terms, it slows down the workflow of logging in to a server. Normal workflow - double-click on the server (we have a software to aggregate all connections in one interface) and enter your password. Your user name would be there already and it's one you used last time. So you only enter a password. Current workflow - you go to user name - change it and only then enter a password. And you do it every time for every server, which is counter-productive. |
|
Nov 8 |
comment |
RDP suggesting a user name when connecting to a server @joeqwerty: It is not substituting the right user (the one you would normally use), all the time. I agree with the fact it is probably not a big deal, but it causes confusion for users, especially for those cases when they normally login locally to domain-enabled server. Now they cannot it (or so it seems). |
|
Nov 8 |
revised |
RDP suggesting a user name when connecting to a server added 320 characters in body |
|
Nov 8 |
asked | RDP suggesting a user name when connecting to a server |
|
Oct 22 |
awarded | Commentator |
|
Oct 22 |
comment |
Is there a way to set access to WMI using GroupPolicy? Good question, I am also wondering on that. |
|
Sep 21 |
comment |
First login is slow in Windows 7 on every PC For reference, in Windows 2012 login of a new domain account takes under 2 seconds. This is the kind of performance I would expect from Windows 7. |
|
Sep 19 |
awarded | Teacher |
|
Sep 19 |
answered | How to Remove a VM From Hyper-V Without Deleting the Configuration File? |
|
Sep 19 |
awarded | Scholar |
|
Sep 19 |
accepted | Get-WinEvent only works on Vista+ as source and target? |
|
Sep 19 |
awarded | Supporter |
|
Sep 19 |
comment |
Get-WinEvent only works on Vista+ as source and target? Yes, speed is the problem - Get-WinEvent can be hundreds of times faster, depending on how many log entries you have. On my test Windows 2003 machine with 10K entries the script runs in 25 sec. My Windows 7 does the same for 40K entries in less than 0.5 sec. I just tried Win2003 -> Win2008r2 and got this error "Get-WinEvent : This cmdlet can run only on Microsoft Windows Vista and later versions of Windows." @ Powershell v2. So far it seems that both source AND target must be Vista+. |
|
Sep 19 |
awarded | Student |
|
Sep 19 |
revised |
Get-WinEvent only works on Vista+ as source and target? added more information |
|
Sep 19 |
asked | Get-WinEvent only works on Vista+ as source and target? |
|
Sep 18 |
answered | Permissions needed to read event log messages remotely? |
|
Sep 18 |
comment |
Permissions needed to read event log messages remotely? @Ansgar: It applies to all log entries, not just some of them. I tried as Domain Administrator, and also as a limited account - and got different outcome. So by raising permission I got from non-working to working. And you are telling me this is not about permissions?.. |
|
Sep 17 |
asked | Permissions needed to read event log messages remotely? |
