Set-MsolUserPrincipalName : Access Denied.

Most of the time, you see the “Access Denied. You do not have permissions to call this cmdlet” error message because of a non-existent UPN name in the “-UserPrincipalName” parameter.

To verify this, you can combine Get-MsolUser and Set-MsolUserPrincipalName cmdlets to include this validation check to get some more meaningful error message.

I suggest you replace “Set-MsolUserPrincipalName -UserPrincipalName $365 -NewUserPrincipalName $email”

with “Get-MsolUser -UserPrincipalName $365 | Set-MsolUserPrincipalName -NewUserPrincipalName $email” and let us know the outcome.

Advertisements

Duplicate Users in Office365

 

Both saying synced with AD however only one account exists

I’ve had to manually delete users from O365 during a DirSync deployment. Use PowerShell on the server running DirSync to run these commands:

Import-Module MSOnline

Connect-MsolService  [Enter your Office 365 admin credentials when prompted]

remove-msoluser –userprincipalname UID@UPN.com

If the account is in Deleted Users in Office 365, append the last command with -RemoveFromRecyclebin

Slow RDS Server

Great article here

Fairshare can reak havoc with certain apps so worth checking out

 

S

Remote Deskop Servies is currently busy

Remote Desktop Services is currently busy

• 20 October 2015
• Simon Godefroy

If you ever see this error when a user is trying to log on to a Remote Desktop Server:

The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.

Log on as an Admin
Load Remote Desktop Services Manager
Switch to “Processes” tab (the user won’t be listed in the Users or Sessions tabs)
End any processes listed for that user

This is usually a Group Policy process getting stuck

Once the processes have ended, the user will be able to log on fine.

 

 

Full credit for the solution here

Install Solus 3 manually

https://community.spiceworks.com/how_to/116689-install-sims-solus-3-agent-manually

Reason 0 – Capita Sims – After Migration

Whilst there a few reasons why reason 0 occurs

“Reason 0” was because under SQL configuration both TCP/IP and Named pipes were disabled for the SQL instance.

On a new install of SQL these are both set as disabled until enabled. It is found in SQL configuration Manager > SQL Server Network Configuration > Protocols for SIMS2012.

Multiple ips on same machine

https://www.loadtestingtool.com/help/how-setup-ip.shtml