Category: Sysadmin RSS feed for this category
Shared folders on windows 7 can’t be accessed from windows XP machines
I had a problem accessing file shares from windows XP machines, it worked at first, but after some time the following error started to occur: \\server\folder is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Not enough server storage is available to process this command. Examining Windows 7 computer event logs, I found following error in system logs: source: srv Event ID: 2017 The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for
Task ‘me@emaildomain.com Sending’ reported error (0x800CCC78) : ‘Unable to send the message. Please verify the e-mail address in your account properties. The server responded: 530 5.7.1 Client was not authenticated’
IMAP and POP3 users with outlook 2003 were getting this error when trying to send mail: Task ‘me@emaildomain.com Sending’ reported error (0x800CCC78) : ‘Unable to send the message. Please verify the e-mail address in your account properties. The server responded: 530 5.7.1 Client was not authenticated’ Since they were connecting to exchange 2010 Hub Transport server as their SMTP server, I had to adjust “Authentication” tab of default receive connector for Client Email. What fixed the problem – unticking “Offer Basic authentication only after starting TLS”. Other possible causes: In outlook account properties Advanced tab untick “This server requires
Configuring Exchange 2010 Autodiscover for internal clients
Problem – internal exchange clients depending on you environment receive one of the following certificate errors/warnings: Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site’s security certificate. The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority. The security certificate has expired or is not yet valid. The name on the security certificate is invalid or does not match the name of the site. most probably you will be seeing the last
New-EdgeSubscription: You can’t use the FileName parameter when running this command.
After installing Exchange 2010 Edge role I have tried to create Edge Subscription file and got the following error: [PS] C:\Users\Administrator\Desktop>New-EdgeSubscription -FileName “c:\edgesusbscription.xml” New-EdgeSubscription : You can’t use the FileName parameter when running this command inside your Exchange organization . At line:1 char:21 + New-EdgeSubscription <<<< -FileName “c:\edgesusbscription.xml” + CategoryInfo : InvalidOperation: (:) [New-EdgeSubscription], InvalidOperationException + FullyQualifiedErrorId : 780CD20B,Microsoft.Exchange.Management.SystemConfigurationTasks.NewEdgeSubscription At first the cause was a mystery to me, but after searching the web I found some clues, reading some posts someone mentioned that they experienced same thing when server was renamed after Edge role installation. This gave me an idea
MSCCM 2012 – Fail to create SQL Server Certificate, ConfigMGR installation cannot be completed.
If you encounter this error “Fail to create SQL Server Certificate, ConfigMGR installation cannot be completed.” while installing Microsoft System Center Configuration Manager 2012, and see something similar to this in your installation log: Failed to get SID for User ‘NT SERVICE\ Try changing the user of SQL SERVER (MSQLSERVER) service to Local System for installation purposes. Links: http://itbl0b.blogspot.com/2011/11/strange-error-while-installing.html
OraClient only administrator can connect to database.
I had this situation in RDSH environment. Application would not connect to oracle database unless the user launching application had administrator rights, or administrator in another session had the application open at the time of regular users were trying to connect. Solution to this is to grant the regular users “Create Global Objects” right via GPO or Local Security Policy. To do this in GPO navigate to: Computer Configuration Policies Windows Security Settings Local Policies->User Rights Assignment Add the groups of users who need to use the application. Links: http://forums.citrix.com/thread.jspa?threadID=68113
Exchange 2010 change default OU for Mail Contacts.
I was not able to find a way to change default OU for Mail Contacts so I’ve changed default OU for user objects in AD. This is not elegant solution, but in my case it’s ok, because all other users are created directly in OU where he belongs and we have no Users Objects created in default users OU in our environment. To change default user OU for Active Directory I used this command on domain controller (in cmd): ReDirUsr “OU=External Contacts,OU=mycompany,DC=domain,DC=com“ Your Domain Controller must be at least in 2003 functional level. Links: http://www.expta.com/2009/03/changing-default-users-and-computers.html
Exchange 2010 change default OU for Distribution Groups.
To change default Organization Unit for newly created Distribution Groups run this cmdlet in Exchange Management Shell: Set-OrganizationConfig –DistributionGroupDefaultOU “OU=distribution groups, DC=domain,DC=local“ Links: http://www.howexchangeworks.com/2011/05/setting-default-ou-for-distribution.html
Exchange 2010 OWA: An unexpected error occurred and your request couldn’t be handled
If you receive this error after installing Exchange 2010 service pack you might want to delete any custom bindings on your Default Web Site in IIS. To do this open IIS Manager, expand your server->sites and select Default Web Site, right click it and choose Edit Bindings… Remove any custom headers you added and it should work right away. Links: http://jaxelos.wordpress.com/2011/12/01/owa-2010-an-unexpected-error-occurred-and-your-request-couldnt-be-handled/
Exchange 2010 OWA errors after SP2.
After installing Exchange 2010 SP2 I started to receive errors in OWA: Your request couldn’t be completed. This may have occurred for security reasons or because your session timed out. This error does not happen if you open OWA via HTTPS. To be able to use OWA via HTTP without this error you need to edit web.config file located in: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\web.config find line: <httpCookies httpOnlyCookies=”false” requireSSL=”true” domain=”” /> and change requireSSL to false <httpCookies httpOnlyCookies=”false” requireSSL=”false” domain=”” /> Save the file and OWA should work fine.
