Welcome to the Lounge

dandy7228-Oct-20 8:12

dandy72

28-Oct-20 8:12

Exactly. It would be the entry in the Start menu showing whatever icon represents the user.

TheGreatAndPowerfulOz28-Oct-20 8:14

TheGreatAndPowerfulOz

28-Oct-20 8:14

Well, it's obvious to you and me, but maybe not so obvious to someone who thinks differently...

#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun

dandy7228-Oct-20 10:07

dandy72

28-Oct-20 10:07

I was not implying it ought to be obvious to anyone.

raddevus28-Oct-20 8:21

28-Oct-20 8:21

Our (work) icon is some generic thing and isn't even a shadow head icon so it isn't obvious and the term "user tile" is terribly generic too. And it is a terrible UI on that Start menu thing.
And over all just terrible interface. Really terrible.

It's esoteric information that if you know, you know. If you don't, you don't.

dandy7228-Oct-20 10:09

dandy72

28-Oct-20 10:09

It's not just esoteric information; some of the so-called Fluent Design ideas are so subtle some people can't see any difference between the very first release of Windows 10, and today's version.

raddevus28-Oct-20 8:19

28-Oct-20 8:19

Thanks I did finally find that. But I don't have the rights to make the changes I don't guess anyways.
Plus the cryptic message that it told me was "click your user tile and choose an option"...
What would that mean? Which option? I wasn't sure. I tried change account settings but I'm not allowed to change it anyways.
I'm helpless and helpless is relaxing. Roll eyes | :rolleyes:

TheGreatAndPowerfulOz28-Oct-20 8:29

TheGreatAndPowerfulOz

28-Oct-20 8:29

What Nelek says...

DerekT-P29-Oct-20 7:51

DerekT-P

29-Oct-20 7:51

I use "Classic Shell" so never see the Win10 start menu. However intrigued by this thread I fired it up (Shift+click start for Classic Shell users) and found the "user tile". There are various options there but NOT to change password. There's a "change account settings" option but that just opens a Control panel screen that again doesn't provide access to a means to change password.

Conversely, using Ctrl-Alt-Del brings up a menu that includes "Change a password" - that does exactly what I'd expect.

TheGreatAndPowerfulOz29-Oct-20 7:56

TheGreatAndPowerfulOz

29-Oct-20 7:56

Yes, you are correct. I was more just informing how to find / use the user tile.

It does seem like a reasonable place to put the change password option though ...

Nelek28-Oct-20 8:21

28-Oct-20 8:21

I have seen really weird things when changing password from remote (or logging in from remote where the password already was expired...)

By the way... I have used the same way with CTRL+ALT+DEL really long, but the most secure way is to go to the control panel >> users >> current user >> change own password

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

raddevus28-Oct-20 8:33

28-Oct-20 8:33

That was very helpful. I was able to get there on another Dev VM where I am an admin.
However, on the main machine I can't get to that because they don't let me be admin.

Anyways, check out the snapshot[^] that shows that I still have to click Ctrl-Alt-Del

it's Ctrl-Alt-Del all the way down!!! Roll eyes | :rolleyes:

Nelek28-Oct-20 9:20

28-Oct-20 9:20

raddevus wrote:
However, on the main machine I can't get to that because they don't let me be admin.

That has nothing to do with admin rights... you are always allowed to change your own password and your profile picture.
If you can't get there, then they have deactivated it on purpose with some idiotic domain policy.

M.D.V.

raddevus28-Oct-20 9:23

28-Oct-20 9:23

Nelek wrote:
f you can't get there, then they have deactivated it on purpose with some idiotic domain policy.

Yes, I said it wrong (don't have rights) but the reality is as you said they've

Nelek wrote:
deactivated it on purpose with some idiotic domain policy.

idiotic is the key word here. Laugh | :laugh:

Nelek28-Oct-20 9:34

28-Oct-20 9:34

raddevus wrote:
idiotic is the key word here.

Are we not speaking about IT? Roll eyes | :rolleyes:

M.D.V.

kmoorevs28-Oct-20 8:44

kmoorevs

28-Oct-20 8:44

Thanks! I learn something new every day! Smile | :)

Now, since you are discussing rdp to a vm desktop, I've a small question. How would this be a security risk to the computer/network at home?

The reason I ask is this: A few months back a customer misunderstood what my company was advertising as a 'cloud solution' for a legacy lob desktop app. (it's actually just the option to post data to one of our web servers for reporting/dissemination, etc.) She was expecting a solution where we host everything...app, data, etc. Remember, this is a legacy desktop app.

When we discovered the misunderstanding (after they had already paid) I suggested that we just create a limited user account on an existing azure vm we have, install the software, and let them rdp in, problem solved. During the process of transferring the customer's files/data, I even asked if they currently use remote desktop for current cloud-based system. The answer was 'yes'.

I went about setting up the account on the server, setting up and configuring the application/files. It works great so I sent the customer the credentials and a setup guide. The response back was a screenshot of the generic rdc not connecting error message. Confused | :confused:

I said she would need to get her local IT staff to troubleshoot it. Within an hour, we had the answer: Company IT forbids Remote Desktop Connections to computers outside of their network. Sigh | :sigh:

They had been the victim of ransomware a few months back and weren't going to make an exception.

So the question is, can an outgoing rdp connection be dangerous for the client? The only way I can think of is through local drives or the clipboard. I'm asking specifically about the MS Remote Desktop Connection here. Thanks for any insight! Smile | :)

"Go forth into the source" - Neal Morse
"Hope is contagious"

Nelek28-Oct-20 9:27

28-Oct-20 9:27

kmoorevs wrote:
So the question is, can an outgoing rdp connection be dangerous for the client? The only way I can think of is through local drives or the clipboard. I'm asking specifically about the MS Remote Desktop Connection here. Thanks for any insight!

We had the issue with RDP in a Windows Server, that the clipboard was shared through all active connected users. The only restriction was, that you had to try to paste things of the same format of the copied ones (by other people).

I mean, if I copied a text, you could paste it in a document on your side.
If you copied a picture I could paste it on paint or a document, but if you copied a file, then I would not be able to paste it until I was in windows explorer.

But AFAIK the clipboard can be deactivated through the settings of the RDP (I can't copy + paste through it in my current job)

M.D.V.

rnbergren28-Oct-20 8:44

rnbergren

28-Oct-20 8:44

#hmm, run some powershell.
$user = "betyacan'tguess"
$current = "J#LOLNope"
$newone = "StillN)pe"
$domain="myown"
$current

$domainname = $domain + ".com"
$dc = (Get-ADDomainController -DomainName $domainname -Discover -NextClosestSite).HostName
$aduser = get-aduser -Identity $user -Server "$dc" –Properties *
$userdn = "LDAP://" + $aduser.DistinguishedName

#$aduserexpire = get-aduser -Identity $user -Server "$dc" –Properties “DisplayName”, “msDS-UserPasswordExpiryTimeComputed” | Select-Object -Property “Displayname”,@{Name=“ExpiryDate”;Expression={[datetime]::FromFileTime($_.“msDS-UserPasswordExpiryTimeComputed”)}}
$lngValue = $aduser.accountExpires
If (($lngValue -eq 0) -or ($lngValue -gt [DateTime]::MaxValue.Ticks)) {
$AcctExpires = "<never>"
} Else {
$Date = [DateTime]$lngValue
$AcctExpires = $Date.AddYears(1600).ToLocalTime()
}

$AcctExpires
$aduser.AccountLockoutTime

#1
Write-Output "pw1"
([ADSI]$userdn).ChangePassword($current,$newone)
([ADSI]$userdn).SetInfo()
Start-Sleep -m 500 -Verbose
#but I didn't send this to you

To err is human to really mess up you need a computer

raddevus28-Oct-20 8:56

28-Oct-20 8:56

I had tried many of these and they all failed on the domain controller I believe.
Tried net user commands too and nothing.

rnbergren28-Oct-20 9:02

rnbergren

28-Oct-20 9:02

not surprised. some companies lock that down to only being ran from a 'server' even a test server minght work though.

To err is human to really mess up you need a computer

Oleg A.Lukin28-Oct-20 20:42

Oleg A.Lukin

28-Oct-20 20:42

Hmm, I always thought that pressing Ctrl+Alt+End on your physical keyboard is the designed way to sent Ctrl+Alt+Del to remote matchine via RDP

Banking establishments are more dangerous than standing armies. T.Jefferson

raddevus29-Oct-20 3:29

29-Oct-20 3:29

Oleg A.Lukin wrote:
pressing Ctrl+Alt+End on your physical keyboard

Yeah, for some reason it wasn't working. I'm remoting from Linux to a Windows box via Remmina (RDP for Ubuntu) and it seems that I can actually send a Ctrl+Alt+Del from that program anyways.
I had to reset the RDP session and then it started working again. thanks

MikeD 229-Oct-20 6:34

MikeD 2

29-Oct-20 6:34

When in remote desktop I believe Ctrl-Alt-End substitues for a local Ctrl-Alt-Del

Edit: beaten to it, couldn't be bothered to read past the end of the page Blush | :O

Peter Adam30-Oct-20 8:49

Peter Adam

30-Oct-20 8:49

Classic solution is press ctr+alt on the keyboard, then del on the on-screen keyboard on the remote machine.

But at the rate they break things in W10 ...

raddevus30-Oct-20 9:45