account management
235 TopicsUsually what is reason for the large 1.5GB RAM usage in Win10?
I have a Win10 question here before it ends on Oct 14. My "task manager" show RAM is 1.5GB in use / 2 GB full. But I did not run/install any apps. The computer "idealpad 110" is quite new. Usually what is the reason for the 1.5GB RAM usage? Thanks a lot.22Views0likes2CommentsExcel xlookup issues after upgrade to version 2509
Excel xlookup is ignoring the references to external file name references after the most recent update to version 2509. I have tried several times to get it to work with no avail. The file with the State name is Warehouse addresses.xlsx and as shown below the current file is named WarehouseList2025-1010.xlsx. Both files are saved in the same folder. Since the formula cannot find a zip code match in column E of the current worksheet, it returns a #VALUE! error.26Views0likes1CommentIssue with emails that I send being rejected by Outlook's postmaster - no fixes work
This has been going on for a year now. Whenever I use my email account to reply to an email, Microsoft's Postmaster rejects it as spam. The only way I can "reply" to emails is to forward that email to another email address that I use (a separate account) and reply to it from there. I have tried numerous times to fix the issue, and none of the methods worked (especially after spending many hours chatting with tech support). I am losing my patience with Microsoft over the matter.19Views0likes1CommentIntune synchronization stopped on all devices
Hello everyone, I’d like to open a discussion regarding a critical issue in our environment. Device synchronization has completely stopped across all endpoints, both inside and outside our corporate network. This started recently and affects every device enrolled in Intune, regardless of connection type or location. We’ve already checked likely causes (network connectivity, service status, and permissions), but sync still does not occur. We also noticed the Windows Task Scheduler isn’t running the jobs that normally trigger Intune sync, which might be related. Has anyone faced a similar situation or can suggest additional troubleshooting steps? Best regards,40Views0likes1CommentWindows 2003 R2 to Windows 2012 R2
It's been a while since I have been on this site. But, I need some help on this one. I have inherited a network that consists of a Windows 2003 R2 server Domain Controller, a Windows 2012 R2 server Domain Controller, and a Windows 2019 server that is not a domain controller, it is an RDP server. My problem is trying to decommission the old 2003 R2 server. Unfortunately there is no sysvol or netlogon shares on the 2012 server. So, I cannot retire it without losing Active Directory. The only thing I can think of is to bring a windows 2008R2 server into the domain to sync AD with FRS then upgrade it to DFSR. I'm pretty sure once I do that I can retire the 2003 R2 server. But that leaves me with another dilemma. That is I do not have a copy of 2008. I looked online and on ebay and I cannot find a copy for a fair price. Most want over $1000.00 and go up to $2000.00. I can find just the install disk, but have no key to activate it. IF anyone has any ideas, please let me know. Thank you Doug30Views0likes1CommentForcing Outlook Fonts via Intune
A client has requested we force a specific font for Outlook on all their devices and I've been investigating a method of pushing this out via Intune. This post on https://www.linkedin.com/pulse/manage-font-intune-outlook-rapha%C3%ABl-zimmermann includes some PowerShell scripts to determine the correct fonts and then apply them, but I'm getting an error when I try to use them. The first script appears to run without incident and provides the font values. $Path = "registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\mailsettings" $Name1 = "ReplyFontComplex" $Name2 = "ComposeFontComplex" $Name3 = "ReplyFontSimple" $Name4 = "ComposeFontSimple" $Name5 = "TextFontComplex" $Name6 = "TextFontSimple" (Get-ItemProperty -Path $Path -Name $Name1 -ErrorAction Stop | Select-Object -ExpandProperty $Name1 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' (Get-ItemProperty -Path $Path -Name $Name2 -ErrorAction Stop | Select-Object -ExpandProperty $Name2 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' (Get-ItemProperty -Path $Path -Name $Name3 -ErrorAction Stop | Select-Object -ExpandProperty $Name3 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' (Get-ItemProperty -Path $Path -Name $Name4 -ErrorAction Stop | Select-Object -ExpandProperty $Name4 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' (Get-ItemProperty -Path $Path -Name $Name5 -ErrorAction Stop | Select-Object -ExpandProperty $Name5 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' (Get-ItemProperty -Path $Path -Name $Name6 -ErrorAction Stop | Select-Object -ExpandProperty $Name6 | ForEach-Object { '{0:X2}' -f $_ }) -join ',' However when the results are run through the below remediation script I get this error: Cannot convert value "0x 73" to type "System.Byte". Error: "Could not find any recognizable digits." At line:57 char:1 + Set-ItemProperty -Path $registryPath -Name $Name1Complex -Value ([byt ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [], RuntimeException + FullyQualifiedErrorId : InvalidCastFromStringToInteger $ValueSimple = "3C,00,00,00,1F,00,00,F8,00,00,00,40,DC,00,00,00,00,00,00,00,00,00,00,00,00,22,43,61,6C,69,62,72,69,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00" $ValueComposeComplex = "3C,68,74,6D,6C,3E,0D,0A,0D,0A,3C,68,65,61,64,3E,0D,0A,3C,73,74,79,6C,65,3E,0D,0A,0D,0A,20,2F,2A,20,53,74,79,6C,65,20,44,65,66,69,6E,69,74,69,6F,6E,73,20,2A,2F,0D,0A,20,73,70,61,6E,2E,50,65,72,73,6F,6E,61,6C,43,6F,6D,70,6F,73,65,53,74,79,6C,65,0D,0A,09,7B,6D, 73,6F,2D,73,74,79,6C,65,2D,6E,61,6D,65,3A,22,50,65,72,73,6F,6E,61,6C,20,43,6F,6D,70,6F,73,65,20,53,74,79,6C,65,22,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,74,79,70,65,3A,70,65,72,73,6F,6E,61,6C,2D,63,6F,6D,70,6F,73,65,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65, 2D,6E,6F,73,68,6F,77,3A,79,65,73,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,75,6E,68,69,64,65,3A,6E,6F,3B,0D,0A,09,6D,73,6F,2D,61,6E,73,69,2D,66,6F,6E,74,2D,73,69,7A,65,3A,31,31,2E,30,70,74,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,66,6F,6E,74,2D,73,69,7A,65,3A, 31,31,2E,30,70,74,3B,0D,0A,09,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,22,41,70,74,6F,73,22,2C,73,61,6E,73,2D,73,65,72,69,66,3B,0D,0A,09,6D,73,6F,2D,61,73,63,69,69,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,61,73,63,69,69,2D,74, 68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72, 2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,68,61,6E,73,69,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,68,61,6E,73,69,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D, 66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,22,54,69,6D,65,73,20,4E,65,77,20,52,6F,6D,61,6E,22,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,62,69,64,69,3B,0D,0A,09,63,6F,6C,6F,72,3A,77,69,6E,64,6F,77,74,65,78,74,3B,7D,0D, 0A,2D,2D,3E,0D,0A,3C,2F,73,74,79,6C,65,3E,0D,0A,3C,2F,68,65,61,64,3E,0D,0A,0D,0A,3C,2F,68,74,6D,6C,3E,0D,0A" $ValueReplyComplex = "3C,68,74,6D,6C,3E,0D,0A,0D,0A,3C,68,65,61,64,3E,0D,0A,3C,73,74,79,6C,65,3E,0D,0A,0D,0A,20,2F,2A,20,53,74,79,6C,65,20,44,65,66,69,6E,69,74,69,6F,6E,73,20,2A,2F,0D,0A,20,73,70,61,6E,2E,50,65,72,73,6F,6E,61,6C,52,65,70,6C,79,53,74,79,6C,65,0D,0A,09,7B,6D,73,6F, 2D,73,74,79,6C,65,2D,6E,61,6D,65,3A,22,50,65,72,73,6F,6E,61,6C,20,52,65,70,6C,79,20,53,74,79,6C,65,22,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,74,79,70,65,3A,70,65,72,73,6F,6E,61,6C,2D,72,65,70,6C,79,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,6E,6F,73,68,6F, 77,3A,79,65,73,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,75,6E,68,69,64,65,3A,6E,6F,3B,0D,0A,09,6D,73,6F,2D,61,6E,73,69,2D,66,6F,6E,74,2D,73,69,7A,65,3A,31,31,2E,30,70,74,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,66,6F,6E,74,2D,73,69,7A,65,3A,31,31,2E,30,70,74, 3B,0D,0A,09,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,22,41,70,74,6F,73,22,2C,73,61,6E,73,2D,73,65,72,69,66,3B,0D,0A,09,6D,73,6F,2D,61,73,63,69,69,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,61,73,63,69,69,2D,74,68,65,6D,65,2D,66, 6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E, 3B,0D,0A,09,6D,73,6F,2D,68,61,6E,73,69,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,68,61,6E,73,69,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,66,6F,6E,74,2D,66, 61,6D,69,6C,79,3A,22,54,69,6D,65,73,20,4E,65,77,20,52,6F,6D,61,6E,22,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,62,69,64,69,3B,0D,0A,09,63,6F,6C,6F,72,3A,77,69,6E,64,6F,77,74,65,78,74,3B,7D,0D,0A,2D,2D,3E,0D,0A, 3C,2F,73,74,79,6C,65,3E,0D,0A,3C,2F,68,65,61,64,3E,0D,0A,0D,0A,3C,2F,68,74,6D,6C,3E,0D,0A" $ValueTextComplex = "3C,68,74,6D,6C,3E,0D,0A,0D,0A,3C,68,65,61,64,3E,0D,0A,3C,73,74,79,6C,65,3E,0D,0A,0D,0A,20,2F,2A,20,53,74,79,6C,65,20,44,65,66,69,6E,69,74,69,6F,6E,73,20,2A,2F,0D,0A,20,70,2E,4D,73,6F,50,6C,61,69,6E,54,65,78,74,2C,20,6C,69,2E,4D,73,6F,50,6C,61,69,6E,54,65,78, 74,2C,20,64,69,76,2E,4D,73,6F,50,6C,61,69,6E,54,65,78,74,0D,0A,09,7B,6D,73,6F,2D,73,74,79,6C,65,2D,6E,6F,73,68,6F,77,3A,79,65,73,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,70,72,69,6F,72,69,74,79,3A,39,39,3B,0D,0A,09,6D,73,6F,2D,73,74,79,6C,65,2D,6C,69,6E,6B, 3A,22,50,6C,61,69,6E,20,54,65,78,74,20,43,68,61,72,22,3B,0D,0A,09,6D,61,72,67,69,6E,3A,30,63,6D,3B,0D,0A,09,6D,73,6F,2D,70,61,67,69,6E,61,74,69,6F,6E,3A,77,69,64,6F,77,2D,6F,72,70,68,61,6E,3B,0D,0A,09,66,6F,6E,74,2D,73,69,7A,65,3A,31,31,2E,30,70,74,3B,0D,0A, 09,6D,73,6F,2D,62,69,64,69,2D,66,6F,6E,74,2D,73,69,7A,65,3A,31,30,2E,35,70,74,3B,0D,0A,09,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,22,43,61,6C,69,62,72,69,22,2C,73,61,6E,73,2D,73,65,72,69,66,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,66,6F,6E,74,2D,66,61,6D, 69,6C,79,3A,41,70,74,6F,73,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,6C,61,74,69,6E,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,66,6F,6E,74,2D,66,61,6D,69,6C,79,3A,22,54,69,6D,65,73,20,4E,65,77,20,52,6F,6D, 61,6E,22,3B,0D,0A,09,6D,73,6F,2D,62,69,64,69,2D,74,68,65,6D,65,2D,66,6F,6E,74,3A,6D,69,6E,6F,72,2D,62,69,64,69,3B,0D,0A,09,6D,73,6F,2D,66,61,72,65,61,73,74,2D,6C,61,6E,67,75,61,67,65,3A,45,4E,2D,55,53,3B,7D,0D,0A,2D,2D,3E,0D,0A,3C,2F,73,74,79,6C,65,3E,0D,0A, 3C,2F,68,65,61,64,3E,0D,0A,0D,0A,3C,2F,68,74,6D,6C,3E,0D,0A" $registryPath = 'HKCU:\SOFTWARE\Microsoft\Office\16.0\Common\mailsettings' $Name1Simple = "ComposeFontSimple" $Name1Complex = "ComposeFontComplex" $Name2Simple = "ReplyFontSimple" $Name2Complex = "ReplyFontComplex" $Name3Simple = "TextFontSimple" $Name3Complex = "TextFontComplex" $hexSimple = $ValueSimple.Split(',') | % { "0x$_"} $hexComposeComplex = $ValueComposeComplex.Split(',') | % { "0x$_"} $hexReplyComplex = $ValueReplyComplex.Split(',') | % { "0x$_"} $hexTextComplex = $ValueTextComplex.Split(',') | % { "0x$_"} IF(!(Test-Path $registryPath)) { New-Item -Path $registryPath -Force | Out-Null New-ItemProperty -Path $registryPath -name NewTheme -PropertyType string New-ItemProperty -Path $registryPath -Name $Name1Simple -Value ([byte[]]$hexSimple) -PropertyType Binary -Force New-ItemProperty -Path $registryPath -Name $Name2Simple -Value ([byte[]]$hexSimple) -PropertyType Binary -Force New-ItemProperty -Path $registryPath -Name $Name3Simple -Value ([byte[]]$hexSimple) -PropertyType Binary -Force New-ItemProperty -Path $registryPath -Name $Name1Complex -Value ([byte[]]$hexComposeComplex) -PropertyType Binary -Force New-ItemProperty -Path $registryPath -Name $Name2Complex -Value ([byte[]]$hexReplyComplex) -PropertyType Binary -Force New-ItemProperty -Path $registryPath -Name $Name3Complex -Value ([byte[]]$hexTextComplex) -PropertyType Binary -Force } ELSE { Set-ItemProperty -Path $registryPath -name NewTheme -value $null Set-ItemProperty -Path $registryPath -name ThemeFont -value 2 Set-ItemProperty -Path $registryPath -Name $Name1Simple -Value ([byte[]]$hexSimple) -Force Set-ItemProperty -Path $registryPath -Name $Name2Simple -Value ([byte[]]$hexSimple) -Force Set-ItemProperty -Path $registryPath -Name $Name3Simple -Value ([byte[]]$hexSimple) -Force Set-ItemProperty -Path $registryPath -Name $Name1Complex -Value ([byte[]]$hexComposeComplex) -Force Set-ItemProperty -Path $registryPath -Name $Name2Complex -Value ([byte[]]$hexReplyComplex) -Force Set-ItemProperty -Path $registryPath -Name $Name3Complex -Value ([byte[]]$hexTextComplex) -Force } I don't know PowerShell well enough to determine what's wrong, but I think the first script isn't providing the values in the right format. While troubleshooting I fed it into Copilot which I think mentioned that some of the output was a string instead of binary. Anyone know what I need to change to get this working?24Views0likes0CommentsIssues with Multiple Microsoft Accounts Using the Same Phone Number
Hi everyone, I’m having a frustrating issue with my Microsoft accounts and hoping for some advice. I have three separate Microsoft accounts, each with a different email address, because I have three separate Minecraft accounts. However, all three accounts are linked to the same mobile phone number. The problem is that every time I try to verify ownership of one account using my phone number, one of the other accounts seems to go inactive or gets flagged. It seems Microsoft doesn’t handle multiple accounts sharing the same phone number very well. Has anyone dealt with something similar, or does anyone know a safe way to manage multiple Microsoft accounts tied to the same number without causing issues for the others? Thanks in advance!43Views0likes1CommentSubject: Microsoft Account “YuBanMe41Day” Compromised — Need Help Submitting Full Evidence
Hi everyone, My Microsoft account (YuBanMe41Day) was recently compromised after I fell for a phishing scam. I know it was a mistake, and I’m doing everything I can to recover the account. I’ve already used the official recovery form, but it doesn’t allow me to include all the evidence I have proving ownership. Here’s what I can provide: - PP account name used for past purchases - Credit card holder information linked to the account - Proof that I’m still partially logged in on my iPad (Microsoft services still show the account, but I’m asked to sign in again when I try to access anything) - Account history such as purchased games, achievements, and activity - Old Gmail and Microsoft passwords and related account information Is there a way to submit this evidence directly to a Microsoft Support agent or escalate the case so it can be reviewed by a human instead of the automated form? I’m worried the standard recovery system won’t accept all the proof I have. Thank you for taking the time to read this — any advice or official contact path would be greatly appreciated. — Nesim16Views0likes0CommentsHP Pavilion Laptop 15-eg2xxx Not Showing in Microsoft Account Devices
Hi, Everyone. I’m facing an issue where my HP Pavilion Laptop 15-eg2xxx isn’t showing up under the “Devices” section of my Microsoft account at account.microsoft.com/devices, even though I’m signed in with my Microsoft account and services like OneDrive and Microsoft Store are working fine. I’ve tried restarting, checking for updates, and signing out/in again, but no success. I’ve also contacted Microsoft Support and was given Case Number 7087906943, but the issue is still unresolved. Hoping someone here can help me figure out what’s going wrong or suggest next steps. Thanks in advance!10Views0likes0Comments