Backtrack:  
Blog
 
showing posts tagged with '2003'
 
Error 0x8007000d in Task Scheduler on Windows 2003 after sysprep
edited by on May 2nd 2018, at 15:43
After performing actions which causes the SID to change (such as sysprep or a DC promote/demote), when opening an existing task in the task scheduler, you may encounter the following error:

Task Scheduler
General page initialization failed.
The specific error is:
"0x8007000d: The data is invalid." An error has occurredattempting to retrieve task account information.
You may continue editing the task object, but will beunable to change task account information.

As a result, it is also not possible to view or change the account information for the selected task.

To work around the issue, remove a saved RSA key, which has been invalidated with the change:

Stop the Task Scheduler s  ...
 
Enable remote WMI access on Windows 2003
edited by on September 16th 2015, at 10:16
If you want to do agentless monitoring of a Windows 2003 host, you need to configure WMI to allow remote querying.

Open Computer Management (Administrative Tools). Expand Services and Applications. Right-click WMI Control, then click Properties.

Select the Security tab, click the Root namespace, then click the Security button at the bottom.

Add the user that will need access to WMI. This is usually the service account running the System Center agent on the host that will monitor this host.When adding the account, be sure to allow for Remote Enable.

If Windows Firewall is in use, you also have to allow for remote management:

Open a command prompt.

Type the following to allow remote mana  ...
 
Setting Out-of-Office for another user on Exchange 2003
edited by on June 16th 2015, at 09:22

The attached VBScript allows you to set an Out-of-Office reply for another user on an Exchange 2003. You'll need the required permissions on the Exchange server to set a user's out-of-office (either Mail Recipients or User Options Management roles).

I found the script in the comments section of this Technet blog article. Special thanks go to the author (Bill Prentice) for sharing.

This script is only for Exchange 2003. Starting from 2007, the Powershell cmdlet Set-MailboxAutoReplyConfiguration is available.

 
NETLOGON wait operation timed out when demoting a 2003 domain controller
edited by on June 10th 2015, at 16:04

When demoting a 2003 domain controller using dcpromo, you may run into the following error:

Error
The operation failed because:

Failed to configure the service NETLOGON as requested

"The wait operation timed out"

The error message is quite misleading as the real cause has got nothing to do with NETLOGON, but is in fact a DNS issue. You will most likely have the server's primary DNS pointing to itself using loopback address (127.0.0.1) or its own IP address.

You can correct the issue by having the DNS point to remaining domain controllers, and remove any DNS pointing to itself (i.e. loopback address or any other IP owned by the server being demoted).

 
Can't log on after changing machine account password in mixed 2012R2 and 2003 AD
edited by on May 28th 2015, at 10:46

When attempting to log on with a domain account on a computer joined to a domain that has both 2012R2 and 2003 domain controllers, you may encounter the following error:

Error message
unknown username or bad password

Additionally, an Event ID 4 on Source: Kerberos is logged. You can only log on using local accounts.

Solution

Mixed 2012R2 and 2003 AD environments require hotfix 2989971 to be installed on every 2012R2 DC. See the KB for a full explanation.

The hotfix requires Update 1 (2919355) to be installed first. The hotfix is also included in update rollup 2984006.

 
 
showing posts tagged with '2003'
 
 
« ‹November 2024› »
SunMonTueWedThuFriSat
     12
3456789
10111213141516
17181920212223
24252627282930
 
Links
 
Quote
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »
Me