Posts made by 1337

Great, so it works if you use RDWeb.

But if you RDP directly to any Windows server or workstation it won't.

@NashBrydges said in Dell Server Not Recognizing Memory:

@Pete-S That's what I also thought. I will have to spend some more time digging all the module numbers out tomorrow once I'm back there. There has to be something mismatched somewhere. Can't imagine anything else at this point.

If possible you should be prepared to swap the CPUs.

What kind of CPUs are in there? E5-26xx V2 something perhaps? V1 is probably more likely.

Troubleshooting quickly adds up so it might be time to consider what to do if the problem can't be solved easily. Like looking at the RAM and reseating it.

R720 is well over it's expected life span at this point. It's very much a possibility that the server is on the verge of catastrophic failure and this is the first sign.

@NashBrydges said in Dell Server Not Recognizing Memory:

The weird thing is that the server is running "perfectly". I add the quotes because while there are no errors and all VMs are working well with no degradation in performance, there is obviously an issue.

This is what to be expected when the CPU doesn't recognize the memory.

What you have is an one CPU with full memory bandwidth and 192GB of memory and the other CPU with 96GB memory and probably only half memory bandwidth. So the server is less performant than it would normally have been.

@NashBrydges said in Dell Server Not Recognizing Memory:

I've also run the Dell diagnostics utility on boot-up and everything checked out ok with a PASS on everything.

The diagnosis utility can't test what the CPU can't recognize or find. So it's of limited value.

@Danp said in Dell Server Not Recognizing Memory:

@NashBrydges said in Dell Server Not Recognizing Memory:

Samsung ECC RDIMMs @ 16GB 1333Mhz memory

Did you notice this is the manual?

NOTE: 16 GB quad-rank RDIMMs are not supported.

Are you able to determine the specific part number for these DIMMs?

I'd check all the small numbers on the DIMMs.

It's possible that someone screwed up and didn't notice.

6x16GB of RAM that is not working is a total of 96GB RAM that is missing. That's a significant amount of the servers total RAM.

It's also possible that one CPU is faulty. Extemely rare though but not impossible. I believe the DIMMs are connected directly to the CPUs internal memory controller.

It's a slightly odd memory configuration so it's not unlikely that it has been upgraded during it's lifetime. Normally it's better to only use 8 DIMMs per CPU and if you need more than 16x16GB use 32GB LRDIMMs instead. Can't mix RDIMMs and LRDIMMs though which is another way to screw up

@PhlipElder

I don't know about RDWeb but it's happens for example when you reset the password in AD, give the user a temporary password and select "Users must change password at next logon".

If you connect with RDP directly to a windows OS (applies to all of them) you can never change your password and you can't login.

I believe it's because RDP need to authenticate the user before the client is allowed to connect and then change their password.

It's been like this since forever, at least Windows 7.

IT support that has remote users should know this. I just need a source from Microsoft I can point them to that explains it to people so they know what to do.

Is there are Microsoft blog post, tech article or whatever place of authority that I can send to IT support people?

I need it for those that doesn't know that you can't force users to change their passwords on first login (or after password reset) when they connect over RDP only.

Users get this error:

As far as I know there is no reasonable workaround around this catch-22 problem.
Except don't force users to change password on first login...

...

...

...

@dafyre said in Bookstack - Line break instead of Paragraph:

@pmoncho Does SHIFT+ENTER work?

Ctrl+Enter is otherwise the usual key combo.

...

@Obsolesce said in DISM /Remove-ProvisionedAppxpackage vs Remove-AppxPackage?:

To save you some time looking through that crAppy code, it basically comes down to two lines, 626 and 640.

I ended up doing something like this:

# apps to remove
$apps = 
   '*549981C3F5F10_*',
   '*GetHelp_*',
   '*Getstarted_*',
   '*Microsoft3DViewer_*',
   '*MicrosoftOfficeHub_*',
   '*MicrosoftSolitaireCollection_*',
   '*MixedReality.Portal_*',
   '*Office.OneNote_*',
   '*People_*',
   '*SkypeApp_*',
   '*Wallet_*',
   '*windowscommunicationsapps_*',
   '*WindowsFeedbackHub_*',
   '*WindowsMaps_*',
   '*Xbox*',
   '*YourPhone_*',
   '*Zune*';

foreach ($app in $apps) {
   Get-AppxProvisionedPackage -Online | where {$_.PackageName -like $app} | Remove-AppxProvisionedPackage -Online 
   Get-AppxPackage -Name $app | Remove-AppxPackage -AllUsers
}

Code needs to run as Administrator.
Removes packages for new users as well as users already on the system.
Windows shouldn't re-install them when you get updates.

@gjacobse said in What Are You Doing Right Now:

Planning out a full de-rack and reconfiguration of the cabinet so the server will fit in it correctly. The front posts are set to far in and the server hits the rear doors…

You could probably just buy a rail depth extender adapter - if that's your only problem.

Sometimes when the racks aren't deep enough you move the front post as much forward as possible but then when you put something new in the rack it sticks out too much and you can't close the front door. Then you have to remove the handles on it or fix it somehow.

Example of adapter:

@gjacobse said in What Are You Doing Right Now:

Dealing with AT&T and Voice Mail issues. For the last few years I seem to have some delivery issues with voicemails being received in a timely manner.

It's sometimes fifteen to thirty minutes to get a voicemail notification on my phone. The kicker was on the 30th taking twenty-five hours before I received the notification.... UN-REAL.

So, reset the network settings, they reset the voicemail completely... I went from a four digit pin to a seven digit pin.. annoying!

And since... I've not received one single voicemail notification. The little message indicator showed nothing. Manually dial voicemail... THIRTEEN MESSAGES!

WH- The- Actual F

So,.. back to the Support calls I go.

There is another way to solve this problem.
You can set up call forwarding to another service, instead of the cell phone providers voicemail.

I do it by forwarding directly to pbx voicemail instead. That way the messages are now in the digital domain. The pbx will email the audio messages, which means I can listen to them without a cell, I can store them, I can forward them to someone else. So many options.

nah...

@travisdh1 said in XO-Lite beta:

I also think having XO Lite available will make XCP-NG more approachable for less experienced techs. I'll still use XO to manage my XCP-NG servers, but XO Lite will make that initial server rollout and XO install more approachable.

For the home lab crowd it will probably be better for sure. But why mess with xcp-ng at all when they can get a full featured web interface with proxmox?

Which is kind of my point. Why even put the effort into a simplified web interface running in dom0 when XO is the real thing and can be deployed with a one-liner? And it comes in a free version.

For me at this point all this is more of an theoretical question though as we are moving to pure KVM instead. I feel that the world is moving towards automation and away from pretty web UI. And also away from self-hosting and towards services that someone else will be responsible for.

@travisdh1 said in XO-Lite beta:

I think the big difference between what XO Lite will be and the web TUI is that you don't need console access, just hit the IP address via a web browser. With how so many other things are moving to the web browser to work or manage, I think it's a good thing for them to be doing.

You don't need console access for the TUI, you have the exact same interface over ssh. You start it by running xsconsole.

@travisdh1 said in XO-Lite beta:

Link to original article: https://xcp-ng.org/forum/topic/4731/xen-orchestra-lite/5

Found this while watching Lawrence Systems Thursday live stream. Most areas of the interface still say (coming soon), but you can do basic tasks for VMs on the host.

I don't know what to think about this web ui feature. There is already a TUI interface for basic management - which you can operate from the console or ssh. Perfect when installaing hypervisors and basic things (like changing network settings, starting stopping VMs etc) because you can use it over IPMI.

And there is the xcp-ng center Windows desktop app, which has all the features that is part of the Xen and the hypervisor itself. Developed by Citrix but not part of Vates' (company behind XO and xcp-ng) business model though.

And there is Xen Orchestra (XO) web app from Free to Enterprise if you want support and the fully unlocked community edition if you don't need support. There you can do things that are not actually part of Xen and the hypervisor itself, like replication. Runs in a VM, not on the hypervisor itself. But there are options to deploy it with a click.

@Obsolesce said in DISM /Remove-ProvisionedAppxpackage vs Remove-AppxPackage?:

@Pete-S said in DISM /Remove-ProvisionedAppxpackage vs Remove-AppxPackage?:

I'm trying to clean up some unneeded Windows 10 apps. But I'm not sure about what method to use.

Does anyone know the difference between using:

DISM /Online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.WindowsCamera_2018.826.98.0...

versus using:

Get-AppxPackage *camera* | Remove-AppxPackage

Dism is an exe, the other is a PowerShell cmdlet.

I don't recall which one, but I think the verb-appxprovisionedpackage is more similar to dism?

I don't remember anymore, it's been like 6 years now since I dove I to it when I wrote the Win10 crApp Remover.

But here's the docs

https://learn.microsoft.com/en-us/powershell/module/appx/remove-appxpackage?view=windowsserver2022-ps

https://learn.microsoft.com/en-us/powershell/module/dism/remove-appxprovisionedpackage?view=windowsserver2022-ps

Awesome thanks!

Links are great, it looks like there is all the information I need.

I can see that you've put in an impressive amount of work making your Win10 crApp remover. I'll take a closer look at how you disable and uninstall things in your code.