Get-logonuser Error Exchange 2010
Contents |
360 games PC games the following error occurred when retrieving user information exchange 2010 Windows games Windows phone games Entertainment All Entertainment microsoft exchange on premises initialization failed kerberos Movies & TV Music Business & Education Business Students & educators get-mailbox the operation couldn't be performed because object couldn't be found on Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet exchange 2010 management console initialization failed Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
The Operation Could Not Be Performed Because Object Could Not Be Found On Domain Controller
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now
The Operation Couldn't Be Performed Because Object Couldn't Be Found On Domain Controller
Hi, I recently was married and changed my name and now EMC 2010 has stopped working. This is the error I am receiving: The following error occured when retrieving user information 'domain\user' The opertation could not be performed because 'SID' couldn't be found on 'domaincontroller.domain.net'. It was running the command 'Get-LogonUser'. Environment is Exchange 2010 Rollup1/ 2008 r2 domain. Any help is greatly appreciated! https://support.microsoft.com/en-us/kb/981033 Nicole Reply Subscribe View Best Answer RELATED TOPICS: exchange 2010 initialization failed Exchange 2010 Initialization failed Error Appearing on exchange 2010   7 Replies Mace OP Jay6111 Jun 5, 2012 at 9:35 UTC How long ago did you make the change? Sounds like it might not have replicated through yet. I'm assuming you can log onto the domain just fine just not https://community.spiceworks.com/topic/231248-exchange-2010-initialization-error-after-name-change open the EMC from your machine? -Jay 0 Poblano OP Nicole7419 Jun 5, 2012 at 9:37 UTC I made the change on Friday so we are thinking it should have replicated, on top of that the secondary DC has been rebooted. I can login and access AD no problems just Exchange is giving issues. 0 Mace OP Best Answer Jay6111 Jun 5, 2012 at 9:52 UTC The error it is throwing is that your user ID SID isn't matching what Exchange knows to be an allowed administrator. You could try removing yourself from the Exchange management security group and then re-adding yourself. If that doesn't work, other than manually editing the attributes of your user ID it would probably be easier and faster to setup another user account with the admin privileges for Exchange and use that. -Jay 0 Poblano OP Nicole7419 Jun 6, 2012 at 9:06 UTC It appears as though EMC is pulling my old name as the security principal and not my new name, any ideas where it would getting my old name from? For example is I try to add an a
I set out to perform a single Exchange 2003 server migration to a new Exchange 2010 server for approximately 200 users. What is a simple task for me had some http://clintboessen.blogspot.com/2011/09/fixed-exchange-2010-single-server.html bumps.I installed setup my new Exchange 2010 server as a brick level deployment http://blog.schertz.name/2010/11/dont-give-up-on-sysprep-yet/ "all roles on one server".I performed the following steps:1. Installed the Exchange 2010 SP1 prerequisites for MBX, HT and CAS.2. Installed the Microsoft Office 2010 filter packs3. Performed the Schema update using setup.com /PrepareAD4. Installed Exchange 2010 with all roles.After installation completed successfully I rebooted the server. After the reboot I noticed exchange 2010 I could not connect to Exchange 2010 using the console or shell. I checked to see if the powershell virutal directory existed... it did not.For some reason only the mailbox role installed, even though the wizard said all roles were installed successfully. I went back and ran setup.exe again. I selected Hub Transport and Mailbox.. went through the install - rebooted. This time all roles existed. be performed because Although Exchange 2010 installed, it was unusable.When I tried to perform powershell commands in the shell as an Exchange organisation administrator I received the following errors:Exception calling "GetSteppablePipeline" with "1" argument(s): "The type initializer for 'Microsoft.Exchange.Configuration.Tasks.Task' threw an exception."+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException+ FullyQualifiedErrorId : DotNetMethodExceptionOpening up Exchange Management Console I received the following error:Initialization failedThe following error occured when retrieving user information for 'user account':Unexpected error [0x17B26A98] while executing command 'Get-LogonUser'.ResolutionTo resolve the issue I performed the following steps:1. Uninstalled Exchange 2010 SP1 from my new server2. Rebooted3. Installed Exchange 2010 SP1 client access server role4. Rebooted5. Tested exchange management console (EMC) and exchange management shell (EMS)6. Installed Exchange 2010 SP1 hub transport role7. Rebooted8. Tested EMC and EMS9. Installed Exchange 2010 SP1 mailbox role10. Rebooted11. Tested EMC and EMSOnly when installing in this order was I able to resolve the issue. Very weird, this is the only time I have experianced this behaviour. Posted by Clint Boessen at 1:49 AM Labels: Exchange 2007/2010 No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Clint Boessen [MVP] clint.boessen@avantgardetechnologies.com.au Clint Boessen's Blog Clint Boessen Perth, Western Australi
the installation of a consolidated Exchange server (with UM) into a new lab network I was immediately presented with this error upon starting the Exchange Management Console. Initialization failed The following error occurred when retrieving user information for ‘SCHERTZ\administrator’: The operation couldn't be performed because objects ‘S-1-5-XXXXX-500’ couldn't be found on ‘dc.schertz.local”. It was running the command ‘Get-LogonUser’. Researching this error returned a handful of articles which were related to either containing a period in the NetBIOS domain name or general time synchronization issues between the Exchange servers and domain controllers. Nothing applied to my environment thus far. Then I ran across a discussion in the TechNet forums that made a light-bulb go off. Using the Systems Internal tool PsGetSid I quickly checked the computer SID of the Exchange Server and compared it to the Domain SID on the domain controller. Oops. Until now I had been using another common System Internals utility called NewSID on every cloned VM I deployed in lab and production environments. But that tool is no longer supported by Microsoft, does not work on Windows Server 2008 (causes blue-screen), and as been officially denounced by it’s author Mark Russinovich. The supported procedure is to use SysPrep but there has been a heated debate on weather that is even needed in terms of changing the machine SID. For the past year I’ve been building and rebuilding lab and demo environments using mainly Server 2008 R2 and have been creating direct clones with duplicated SIDs and had not run into any issues. That includes various beta, release candidate, and RTM installations of Exchange Server 2007, 2010, OCS 2007, and Lync 2010. Typically I would use a combination of Windows Server versions and editions so often I was side-stepping the issue by having different source installations for the domain controllers and member servers. In this specific environment I used the same Server 2008 R2 Enterprise image for all servers. Clearly I need to go back to using Sysprep as Exchange is not happy. But in the meantime I