User Profile
Surfer10
Copper Contributor
Joined Apr 01, 2020
User Widgets
Recent Discussions
Outlook 365 keeps asking for credentials
Something very strange is occuring. Suddenly my Outlook 365 is asking for credentials. When i give in my credentials it comes back to fill it in again. We are working with Office 365 and on-premise Exchange 2013. 1. What i have tried is to delete the profile in Outlook, then when making a new profile it asks for credentials but does not accept credentials. 2. Delete credentials thru credentials manager in Windows 10 3. Added some registry keys found on the Internet: DisableAADWAM - DisableADALatopWAMOverride 4.Added some other registry keys found on the internet to prevent the credentials asking 5. Deleted the content of %appdata%\microsoft\Outlook and %localappdata%\microsoft\Outlook Hours spend but still cannot use Outlook anymore that is not on new systems. Because i have Outlook already running on a WIndows 10 system, it keeps running. Windows 10 version is 2004, The systems where i have troubles with credentials are Windows version 20H4 so i believe it has something to do with the Windows version i use. Someone a idea?1KViews0likes0CommentsRe: quick assist deployment thru Powershell-GPO
Hi bgiroux, When i do this under account administrator dos prompt it gives me a error (when running batchfile it does nothing so i give the dism command in a elveated dos prompt) : Image version: 10.0.19043... Error: 2 The system cannot find file specified. Logfile can be found....17KViews0likes0Commentsquick assist deployment thru Powershell-GPO
Since that Microsoft is turned with quick assist to the Windows Store we cannot use Quick assist anymore. I cannot install / deploy it thru Powershell whatever i try thru GPO, manual, scheduled task etc, it will not work. The only way that the install succeeds is when go to the Store and download and install it when i am an admin. But i want to deploy Quick Assist thru Powershell... What i tried: #sets switches param ( [Parameter(Mandatory=$false)][Switch]$Install, [Parameter(Mandatory=$false)][Switch]$Uninstall, [Parameter(ValueFromRemainingArguments=$true)] $args ) #Log output results function LogOutput($Message) { $LogFile = "C:\temp\Quick-Assist.log" "$(get-date -Format 'MM/dd/yyyy HH:mm') $($Message)" | Out-file -FilePath $LogFile -Append -Force } #Start of Script If ($Install){ Try { LogOutput "***This script is used to install the new Quick Assist app that is from the Microsoft Store. It will also remove the old version***" $InstallAppX = Get-AppxPackage -allusers MicrosoftCorporationII.QuickAssist If ($InstallAppX.status -eq 'OK'){ LogOutput "[Info] Windows Store version of Quick Assist is already installed" #lets uninstall the old version. LogOutput "[Info] lets uninstall the old version" Remove-WindowsCapability -Online -Name 'App.Support.QuickAssist~~~~0.0.1.0' -ErrorAction 'SilentlyContinue' LogOutput "[Info] Old version of Quick Assist has been uninstalled" } If ($InstallAppX.status -ne 'OK'){ LogOutput "[Info] Installing the Windows Store version of Quick Assist..." Add-AppxPackage -Path "c:\quickassist\MicrosoftCorporationII.QuickAssist.AppxBundle" #Add-AppxProvisionedPackage -online -SkipLicense -PackagePath '.\MicrosoftCorporationII.QuickAssist.AppxBundle' LogOutput "[Info] Attempting to remove the old version of Quick Assist..." Remove-WindowsCapability -Online -Name 'App.Support.QuickAssist~~~~0.0.1.0' -ErrorAction 'SilentlyContinue' } LogOutput "[Success] The Windows store version of Quick assist has successfully installed and the old version has been removed." } catch [exception] { LogOutput "[Error] An error occurred installing Quick Assist: $($_.Exception.Message)" } } We are using windows 10 21h1-2 Problem with this script is also that it says it removes the old version and installed the new version successfully, and when i look with get-package.... it also states that quick assist package is installed, but it is not in the startmenu anymore.... How can i deploy quick assist best for many computers without Intunes or sccm?18KViews0likes5CommentsRe: connecting to exchange 2010 server
tried another client and used powershell 7 now the error is: Connecting to remote server server.domain failed with the following error message : De WinRM-client heeft een HTTP-statuscode 403 ontvangen van de externe service WS-Management According to microsoft this error is because SSL is enforced on the powershell module on exchange but this is not the case. Emtshooter gives the same message when executing it from the other client in pshell 7: account is not configured for remote powershell, but unfortunally it is.3.2KViews0likes3Commentsconnecting to exchange 2010 server
A long time i connected to exchange on premise 2010 server from a client. The command to connect (run powershell as admin or special user which has rights to exchange remote): $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos -Credential $UserCredential In stead of "powershell" i fill in the fqdn of the exchange server. This always worked but not anymore. I do not know what changed locally or on the exchange server but this is the error: New-PSSession : [servername.fqdn] Connecting to remote server fqdn failed with the following e rror message : Cannot connect to the destination that is given on request. Check that the service is running on the destination and accepts requests. Read the log for wsman, check the management service which is stared on the destination (usually WINRM or IIS, if it is winrm start winrm quickconfig. see the about_Remote_Troubleshooting Help topic. At line:1 char:12 + $Session = New-PSSession -ConfigurationName Microsoft.Exchange -Conne ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed the exchange 2010 server is accepting requests, winrm quickconfig says this and is running. I have downloaded and started emtshooter to see what the problem could be: emtshooter says that the account that is running does not have exchange remote access. To check this run the following command on exchange: (get-user domain\user).remotepowershellenabled for all the users which i use in Powershell it says enabled (this is very strange) i have tried users with domain without domain and fqdn but they all have remotepowershell enabled. What can this be, if it is not the Exchange fw?3.8KViews0likes12Commentsadd ad users to a ad security group input from msol accountskuid
I am trying this command to first geet the users in Azure who have a standardpack license and then add tthos users to a on-premise AD security group. The users which are retrieved from Azure are corrcect, that part works but then adding them to the aad-adgroupmember does not does the job. It runs but for all users it gives a result: migrate: false. So the script is not faulty but i am giving the wrong input or something like that? The goal is to assign ad users autmatically a office E license based on security group in AD, then when a user leaves the company or is new it will be automatically assigned that license.. The script: $msolUsers= Get-MsolUser -All | Where-Object {$($_.licenses).accountskuid -eq 'company:STANDARDPACK'} ForEach ($user in $msolUsers) { try { $ADUser= Get-ADUser-filter {UserPrincipalName -eq $user.UserPrincipalName}-ErrorAction stop Add-ADGroupMember-Identity O365-E1 -Members $ADUser-ErrorAction stop [PSCustomObject]@{ UserPrincipalName = $user.UserPrincipalName Migrate = $true } } catch { [PSCustomObject]@{ UserPrincipalName = $user.UserPrincipalName Migrate = $false } } }Solved958Views0likes1CommentRe: add computers to security group automatically
Now tht the script works is there also a way to exclude some names with DESKTOPNR? I would like to run this command every week so that computers which are not a member of the testgroup will be added as member but there are 10 computers with the name dekstop111, desktop112,desktop250 and so 10 total. Is it possible to exclude these, these 10 computers must be added to another group: prodgroup.14KViews0likes1CommentRe: add computers to security group automatically
farismalaeb I think it is version on a WIndows Server 2012 en the version on my WIndows 10 client is 5 i believe, which comes standard with Windows 10. On both Powershell versions the last is also not working, it gives no error but it does nothing, i hope you have some more suggetions: $AllPC=Get-ADComputer -Filter 'Name -like "desktop1"' -properties displayname foreach($SinglePC in $AllPC){ add-adgroupmember -identity "testgroup" -Members $SinglePC.SamAccountName }14KViews0likes5CommentsRe: add computers to security group automatically
farismalaeb Hi, this is what i get: Method invocation failed because [Microsoft.ActiveDirectory.Management.ADComputer] does not contain a method named 'foreac h'. At line:1 char:1 + (Get-ADComputer -Filter 'Name -like "desktop1*"' -properties displayname ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (foreach:String) [], RuntimeException + FullyQualifiedErrorId : MethodNotFound Must there be a $ at desktop1$14KViews0likes9Commentsadd computers to security group automatically
I would like to add computers in AD with names that start with desktop to a security group: testgroup. We would like to run this powershell command thru scheduled tasks to run every week so that if someone forgets to add the computer to the security group it will be done. Every computer with name desktop must be aded to that group. I have the following: Get-ADComputer -Filter 'Name -like "desktop*"' -properties displayname | add-adgroupmember -identity "testgroup" When i run this it asks for a members(0) How can we accomplish this? I would like to first test it with desktop1 in stead of *.Solved14KViews0likes12Comments
Recent Blog Articles
No content to show