When creating a new Receive Connector on Exchange Server 2007 SP3 (Update Rollup 2) the creation failed with a non-retriabele error and a “the requested attribute does not exist” error:
Active Directory operation failed on GL-SRV.test.local. This error is not retriable. Additional information: The parameter is incorrect.
Active directory response: 00000057: LdapErr: DSID-0C090C26, comment: Error in attribute conversion operation, data 0, v1772
The requested attribute does not exist.
Exchange Management Shell command attempted:
new-ReceiveConnector -Name ‘mail.gltest.com’ -Usage ‘Internet’ -Bindings ‘0.0.0.0:25’ -Fqdn ‘mail.gltest.com’ -Server ‘GL-SRV’
Elapsed Time: 00:00:00
According to this article on the Microsoft Exchange Team site more people are facing this issue (scroll through the comments). It looks like something specific to UR1 and UR2 for Exchange Server 2007 SP3:http://blogs.technet.com/b/exchange/archive/2010/09/09/3410985.aspx
Microsoft is aware of this issue and it is currently being investigated. It looks like the schema upgrade during SP3 is not performed properly sometimes, resulting in an incorrect schema for Service Pack 3. Unfortunately the setup application of SP3 continues, resulting in these kind of errors.
You can solve it by running the Exchange 2007 SP3 schema upgrade again:
After this creation of a new Receive Connector is successful.
Click Start, click Run, type “regedit” in the Open box, and then click OK.
In the left pane, locate and then click the following registry subkey:
On the Edit menu, click “Permissions”.
In the “Permissions for Installer” dialog box, consider the “Administrators” and the “Users” in the “Group or user names” list.
Make sure that the Full Control permission is set for the “Administrators” and the “Users” group.
If this permission is not set, click to select the Full Control check box under “Allow”.
After installing Remote Desktop Web Services, one of the first things that I wanted to do was remove the requirement to put the domain name in. I am in a single domain environment and do not have a need for users to have to qualify their domain. I found the following fairly simple fix:
– Find the file renderscripts.js which for me was located in: C:WindowsWebRDWebPagesrenderscripts.js
– Find the function onLoginFormSubmit()
– Find the lines:
if ( objForm != null )
strDomainUserName = objForm.elements("DomainUserName").value;
– Copy/Paste the following code after the lines above:
// add default domain...
if ( strDomainUserName.indexOf("\") == -1 )
strDomainUserName = "YOUR_DOMAIN_NAME\" + strDomainUserName;
objForm.elements("DomainUserName").value = strDomainUserName;
– Save the File.
A new server has been added to the forest as a new domain controller, on the new server after launching PowerShell command line, Use the Move-ADDirectoryServerOperationMasterRole command to transfer all the FSMO roles. Each role corresponding to a number :
Move-ADDirectoryServerOperationMasterRole -Identity “DC01” -OperationMasterRole 0,1,2,3,4
- Set valid password for vi-admin, for example F0t56otk!# should do
- Login to vMA shell as vi-admin
- Elevate session as root with “sudo –s”
- Run “pam-config –d –-cracklib” (note double dashes on front of cracklib)
- Exit root shell with “exit”
- Change vi-admin password with “passwd” to any password you’d like
Above pam-config command disables cracklib in vMA PAM (pluggable authentication module) configuration, cracklib is a PAM library which is used to enforce Linux, and it this case vMA account password strength.