PowerShell cmdlet/parameter combinations are unsuccessful in Exchange Server 2016
Hello All, I notice this weird error from Exchange powershell while running this cmdlet:- Get-MailboxJunkEmailConfiguration -Identity "user@contoso.com" Error:- Error on proxy command 'Get-MailboxJunkEmailConfiguration -Identity:'user@contoso.com'' to server Ex01.corp.contoso.com: Server version 15.01.1713.0000, Proxy method RPS: The operation couldn't be performed because object 'Ex02.corp@contoso.com' couldn't be found on 'ADcorp.france.contoso.com'.. + CategoryInfo : NotSpecified: (:) [Get-MailboxJunkEmailConfiguration], CmdletProxyException + FullyQualifiedErrorId : Microsoft.Exchange.Configuration.CmdletProxyException,Microsoft.Exchange.Management.StoreTasks.GetMailboxJunkEmailConfiguration The following correctly applies to my Exchange environment:- Microsoft Exchange Server 2016 environment that contains two or more mailbox servers. Active Directory Forest contains two or more domains. Exchange Servers and user objects are located in different Active Directory domains. I manage recipients through Exchange Management Shell (EMS) by setting “Set-ADServerSettings -ViewEntireForest $true”. I found this article - https://support.microsoft.com/en-us/help/4295103/powershell-cmdlet-parameter-combinations-don-t-work-with-exchange-serv For this issue, User is located in a different AD forest than my admin account, also I am running the command from a different Exchange server than the one user mailbox is in. I have full admin rights and all necessary admin roles, organizational management,..etc no issues. I usually use Set-ADServerSettings -ViewEntireForest $true” to manage these user objects. For this issue, when i specify the AD server that user object resides with parameter -DomainController (Get-MailboxJunkEmailConfiguration -Identity "user@contoso.com" -domaincontroller ADcorp.spain.contoso.com) it works well. But when I don't, I have this error, and what is weird is that I am getting this error only for this particular cmdlet "GetMailboxJunkEmailConfiguration" and perhaps others listed in above article. If I do any other command, e.g get-mailbox, get-calendarprocessing etc, I don't need to specify the -DomainController and it works fine without errors. It's very strange, I dont know if anyone else have faced this issue, why its only happening to certain cmdlets in Exchange 2013/2016? There doesn't seem to be much info about it apart from that article above saying to use the -domaincontroller as workaround.Windows AutoPilot - Failed to Install last app (alt+tab shows Visual C++)
Hello everyone. We're running a deployment of Windows AutoPilot (we've done for a fair chunk of clients now successfully) however, we've one instance that we're not able to get around. On installing the apps it sometimes (Behaviour 1 below) fails on an app. Some times it goes through fine but prompts for install once completed deploying (Behaviour 2 below) Behaviour 1 of 2: While deploying and on the Enrollment Status Page - it is showinf 7/8 apps installing, and then after an hour or so it fails. If I press and hold ALT+TAB while it is on the deployment phase of the apps. it shows Visual C++ 2010 in the background trying to prompt the user to accept the license tersms and requing user to click install. - Even though you hold down ALT+TAB you can't actually switch to this to continue to accept the license and install the Visual C++ installation. You are left with the deploying failing and the user needs to click "Continue anyway" at the bottom. When you click continue anyway, it opens up the desktop and you need to then accept the license terms and install Visual C++ 2010. Win Version 1903 Behavious 2of 2: While deploying and on the Enrollment Status Page it passes 8/8 apps and then goes straight to the desktop desktop and you need to then accept the license terms and install Visual C++ 2010. Win Version 1909 I understand one of the apps ovbiously requires the Visual C++ to install - not sure how we bypass this behaviour so there is no need for user intervention to complete this part. Many thanks for reading through. ASurface Hub managed by Intune & Licensing via EMS
We have a few Surface Hubs in our organization which I'd like to add to intune. Obviously these devices should not be associated with a specific user, so I started looking into the Device Enrollment Manager (DEM) feature as a way to join the devices w/o tying them to a user. Reading the doc on DEM (https://docs.microsoft.com/en-us/intune-classic/deploy-use/enroll-corporate-owned-devices-with-the-device-enrollment-manager-in-microsoft-intune) leaves me with the impression that each device enrolled using a DEM requires it's own intune license. We get intune as part of EMS, which is licensed per user, not per device. Do we need to buy additional per-device intune licenses for each surface hub? Or, am I on the wrong track altogether? Is there a better way to enroll the Hubs in intune w/o a user association?
