I installed Microsoft Exchange 2010 SP3 on Windows Server 2008 R2 successfully but when I try to expand the Microsoft Exchange On-Premises the initialization fails with the error
Initialization Failed
The following error occurred when retrieving user information for 'Domain\User': The operation could not be performed because Domain\User could not be found.
Initially I thought it to be the issue related to KB982639 but that doesn't seems to fit here, other then this I have no clue to what the issue could be.
Any lead is appreciated.
Well, such issue is probably due to the same SID of the domain machines or the AD/DC and one of the machine or all of the three. For me when I faced this issue the problem was that I cloned all the 3 machines from the VM Template and did not run sysprep properly which caused the conflict. As the AD recognizes the machines from SID it couldn't recognize the machine and this could not retrieve the user information causing the "Initialization Failed".
Solution
Run sysprep on all the 3 machines with generalize option checked. sysprep can be found in C:\Windows\System32\sysprep\. Unfortunately, you have to destroy the current setup you have as you have messed up with the user info in Active Directory.
I am encountering this error, "100024 The encryption passphrase provided does not match with passphrase associated with the following server: %ServerName Please update the server settings with the current passphrase for data encryption." I used the passphrase generator in the install wizard and I used the same from the Azure Backup GUI - e.g. "Register". Created phase phrases many times. Uploaded a self-signed certificate to Azure Backup. I installed, uninstalled and installed again MARSAgentInstaller.exe several times. The agent installer is installed on a domain controller. The server has Windows Server 2012 R2 Essentials running. The "Download Agent for Windows Server Essentials" (OnlineBackupAddin) was run. Much googling was done. Every combination imaginable was tried. The error remains and backups cannot be performed. Any solutions, suggestions or hints will be greatly appreciated.
this is my first time using Linux, and I'm shooting in the dark here.
I'm using Ubuntu 14.04 LTS and the latest version of Rstudio Server.
After much trial and error I finally managed to join my company's local domain, which enables network users to log into the Linux machine.
I have no problems logging into the Rstudio Server using a local account, but I can't log in using a network user account.
I've been on many help pages (below) but they haven't been much help:
Password Database for RStudio Server?
NIS/AD Authentication with RStudio Server
Deploying Rstudio Server for Classrooms
RStudio Server - Log-in and User Authentication Problems
Accesing RStudio using domain credentials
Any help or directions would be greatly appreciated.
I know it has been a while, but I just stumbled upon your question.
Probably it not relevant any more, nevertheless, I will briefly contribute.
Since you are a first time Linux user, I assume that you didn't make the investment of buying into the RStudio Server Professional Edition.
Active Directory user login is not available for the Open Source Edition. Only local users are allowed with the Open Source Edition.
I've just created two Windows VM's in Azure, one 2012 Datacenter and a 2008 R2 SP1 and i am not able to connect via remote desktop to either of them. Both machines are running under the same cloud service and the RDP ports are mapped to two distinct public ports. Every time i try to connect i get the error message "The logon attempt failed".
Using NMAP in a Linux VM i also have there, i was able to check that the port 3389 is OPEN in both machines. Also, the public RDP ports respond correctly (e.g. are open).
I tried to enter using two different Windows 7 client machines, also with no lock. MSTSC version is 6.3.9600.16415, in both machines. I've used both the .rdp file, downloaded from the "Connect" option in the windows azure dashboard and a brand new RDP connection created by me - same result.
I've tried also to upgrade the VM size from small (1 core, 1.5 GBRam) to medium (2 cores, 3.6 GBRam), restart, setup a new clean windows VM, with different credentials... nothing changed, same result.
The really odd thing is that i was able to connect, after several failed attempts, to one of the VM's, the 2012 one, but only one time - after that, no luck, always "The login attempt failed".
What worked for me was changing the RDP login screen to use a different account, and use the "local account" which is the name of the VM and the username, like so:
TheVMName\TheAdminUsername
Where TheVMName is the name of your VM, and TheAdminUserName is the admin user name you used for that machine.
I was able to find/confirm the latter on the Reset Password screen under the SUPPORT + TROUBLESHOOTING section on the left.
Since Windows 10, you need the domain is automatically set to MicrosoftAccount followed by your email address as username. MicrosoftAccount\My#UserName.com
Instead, the username is like UserName.com\My.
This worked for me.
I have no idea why, but the solution is simple (works every time, at least for me): I was copy-pasting the passwords from a KeePass, as i use this to generate and maintain the huge amount of credentials i use one way or another.
SOLUTION: instead of copy-paste, type the password
The drawback is that i have to use simpler passwords for this access
I've tried to login and failed using windows 8.1 Pro to an azure vm. The message I got repeatedly was "Login Attempt Failed". So my specific problem wasn't that i couldn't connect to the machine but that it couldn't authenticate...even though my my Administrator username and password were correct.
The way I logged into the machine was to provide the host name then the username:
Host\Username
My Azure account did not have a domain controller setup.
It was simply looking for it's local host machine name.
This link helped: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-log-on-windows-server/
May be following can help:
In this screen please select the option "Use a different account":
Further type in "Domain\Username"
TIPS:
- The "Domain" can be found on the "Overview" page for your VM in Azure. It's appearing as:
Public IP Address: [SomeIPValue].
- If you do not remember or have "Username" & "Password".The local admin "Username" & "Password" can be set to get access under:
Azure -> Your VM page -> Support + Troubleshooting -> Reset Password.
I've had a similar problem and it turned out that my password wasn't complex enough.
It was really confusing that Azure Portal even let me create a VM with such a password.
It was resolved by going to the VM page -> Support + Troubleshooting -> Reset Password and specifying a more complex password (both case letters, numbers, special characters and doesn't contain username).
Thanks to Jagjit Singh whose answer pointed me in the right direction. Hope this helps somebody.
I found that, while creating VM, if we put password without any special characters, then it still accepts the password but the login to the VM will fail using that password. It gives an error "The logon attempt failed".
It may work after the "Reset password" option but sometimes it shows "Failed to reset password".
So better to put a proper password.
I know this question is too old, answering for new visitors.
Easy solution would be, you can try to add new user or reset the password from Azure Portal
This will add the user if it does not exist, and you can try logging in with new account.
Issue : "The logon attempt failed". ( Windows azure Machine)
I have tried multiple option didn't help, hence updating this as correct answer , it worked for me .
Solution :- While creating the password/updating for windows azure vm create the password as recommended by Azure with prescribed. Main issue with password .
Steps as below for Issue fix.
Once logged in Azure portal, click on VM windows machine , go to (Support and Troubleshoot)
update the password as recommended by Azure as below
(Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character.)
Password :- updated as 13 char which include 1 Capital, Lower Case and Special ,1 number .
Password:- Azureuser#123
After updating the password as Microsoft Suggested it worked for me and able to connect windows machine as below
Able to connect as below
Try about method it should work, if issue please suggest.
We need to have strong password when we create user account for VM ..
It was annoying when I encountered this.I was only succeed when I reset my password step. Issue with portal allows is to create week password while creating VM and validation rules are different while RDP to using week password.Same validation rules applies when we re-setting password.
I am in need of help getting Local Development STS running. I just started with MSDN tutorials and got stuck when trying to build WCF service using WIF. So far I did following:
Installed "Identity and Access Tools" in my Visual Studio 2012
Created new WCF Service project in new solution
Right clicked projects name and selected "Identity and access..."
Selected "Use the Local Development STS" option on first tab and changed token
type to "SAML 2.0" on "Local Development STS" tab
Clicked "Ok"
I end up with following that informs me about problems with certificate:
I verified that the file is there physically.
I verified access to it - System, Administrators and my user have full access to it (only last option is unchecked)
I tried to install the certificate manually, but it is protected with password and I cant find it anywhere
I tried to toy around with "Identity and Access..." wizard
I tried to google the answer
I tried to check if I have certificate like that installed, there are tree Personal certificates in my Local Machine store, but I have no idea how to check their subject or whatever else
So far I wasn't successful. Could anyone advise how to fix the situation, so I can be sure I have proper certificate installed, I would be eternally grateful.
Erchi
Are you using the .NET 4.5 tutorials - WIF Code Sample Index?
To check the subject:
Start / Run / mmc
File / Add - Remove Snap In
Certificates - Add.
My User Account - Finish - OK
Expand the tree as required - double click on certificate - Details.