Saturday, October 30, 2004
Wednesday, October 27, 2004
Tuesday, October 26, 2004
Friday, October 22, 2004
Set /a 0x7a
Next step might be to convert it into an error message:
Net helpmsg 122
This can be done in a one-liner:
Set /a e=0x7a & (net helpmsg %e%)
Note the parenthesis – without, the e environment variable does not exist when net… is parsed by the interpreter. With parenthesis, it is treated like a separate line.
If you get an error number like -2147024891, you have to remove the upper 16 bits before you get the real error number:
set /a "-2147024891 & 0xffff"
Note that the quotes are necessary to treat & like a bit-wise and.
If you don't know the You had me at EHLO... blog i would suggest that you check it out - IMHO it's a must read for everyone working with Exchange.
Thursday, October 21, 2004
In Windows Server 2003, administrators can change the computer name of a Windows Server 2003 domain controller by using My Computer or Netdom.exe, but neither method renames the domain controller's corresponding NTFRSmember object for SYSVOL from the old computer name to the new computer name. The difference between a domain controller's NetBIOS name and the common name for its NTFRSmember object does not break any functionality until a new domain controller is promoted into the forest with the old NetBIOS name of the renamed domain controller. When this behavior occurs, the new domain controller deletes the existing (duplicate) NTFRSmember object and recreates a new NTFRSmember object for itself. The renamed domain controller that originally created the NTFRSMember object ends up without an NTFRSmember object.
Read the rest in this KB
Wednesday, October 20, 2004
I've just finished recovering a SBS 2003 Exchange installation from the results of an antivirus scanner which found a variant of Netsky in the e00.log file (The "working" log file in use by exchange, which will be renamed to Exxxxxxx when it reaches 5.120 KB) and deleted it - resulting in a dirty shutdown and an -1811 error from Exchange which prevents mounting the Store.
The person who installed it had excluded the catalogs containing the .EDB files but had forgotten to exclude the catalog where the log files resides - so when you configure this remember that the Exchange Stores and their log files can be placed in many different directories and also to exclude the SRS folder.
To make things worse the Anti-Virus client was configured to delete files instead of quarantining them (so I weren't able to recover the file) and the customers last backup was more than 5 days old. So I had to do a full repair of the databases (Luckily there wasn't any serious corruptions - it was primarily inconsistencies due to dirty shutdown and the missing log file).
This time I used the dial tone restore method, which starts by creating a blank database so all the users got access to e-mail (Sending and receiving new mail, not old e-mail or public folders), while I had the time to repair the old Information Stores and mounting them in a RSG for testing. Afhter this I switched the Dial tone Mailbox Store and the now repaired Mailbox Store around between the Storage Groups and ran Exmerge (The purpose of switching databases is that you retain all outlook rules etc. and just has to Exmerge the content of the smaller Dial tone Store into the older/repaired Store).
Check this page for 4 security best practices for Exchange - including info and links to articles on configuration of filebased antivirus scanners and what to do when everything has gone wrong.
Tuesday, October 19, 2004
Monday, October 18, 2004
Wouldn't it be great to be able to test new servers immediately, without formatting hard drives, using Virtual Something or dedicating one or more computers to the project? Now you can, with the TechNet Virtual Lab
Thursday, October 14, 2004
Microsoft has a reference at MSDN. But I know for sure, that it is not complete. Anyway, it is a good starting point.
Wednesday, October 13, 2004
Is Linus Torvalds secretly working for Microsoft? That sounds crazy until you consider that lately, the free operating system he created, Linux, has been helping Microsoft close deals.
Read the rest of this article. Beware of the annoying ads.
Interesting WebCast for those of you new to Hosted Exchange 2003 and/or those of you who have already created your own hosting solution based on Exchange 200x -
This Support WebCast discusses Windows-based Hosting, including Hosted Exchange 2003 ... Hosted Exchange 2003 enables service providers to offer flexible and scalable rich e-mail, messaging, and collaboration services to consumers, and to both small and medium businesses. Hosted Exchange is a tested, pre-engineered solution that is based on standard Microsoft server products ... The Support WebCast also reviews the important components of the solution and addresses common challenges in the hosting world. This includes multi-tenancy (address isolation between customers), automation and provisioning (creating new customers by using automation and without the RUS), client auto-configuration for Outlook by using RPC over HTTP, active user reporting, three-year CALs versus Service Provider Licensing Agreement, multiple services per hosted organization, and user namespace per organization.
Tuesday, October 12, 2004
As you may know (kb252398 and KB257341) you cannot grant dial-in access to a user simply by setting the msNPAllowDialin property on the user object in Active Directory. For some reason this attribute must be synchronized with information in the userParameters blob – sic!
Instead of chasing a way to make this happen, simply ask your Windows Server 2003 IAS server to ignore the dial-in attribute and stick to group membership or whatever you feel like. This is done by setting Ignore-User-Dialin-Properties on the remote access policy. For more information click here and read the section called Ignoring the dial-in properties of user accounts.
Saturday, October 09, 2004
Wednesday, October 06, 2004
... Our initial investigation has revealed that the vulnerability could allow an attacker to bypass authentication on a Web site running ASP.NET applications on Windows 2000, Windows 2000 Server, Windows Server 2003, Windows XP Professional by sending a malicious request to a Web server. This could allow an attacker to make changes to the content of a Web site, but would not allow the attacker to control the computer or run software on it.
... Microsoft is providing this prescriptive guidance in order to inform customers as quickly as possible about the vulnerability and information on how to prevent an attack. Microsoft is actively investigating the issue and plans to release additional guidance
Cool new tool from Microsoft – spotted at You Had Me At EHLO...
ADModify is a tool that was (and is still) developed and maintaned out of our Support Services (aka PSS) team, and was created to make it easier to modify / import / export objects in Active Directory in bulk .... ADModify.NET (v2.0) was written from the ground up using Visual C# .NET 2003. When benchmarked against its predecessor, it made the same modifications in less than half the time. Its new feature set allows administrators to bulk modify any AD attribute from any AD partition with almost limitless flexibility.
Microsoft released their Exchange Server Best Practices Analyzer tool to the web. The tool in different versions has been used for quite some time by PSS and is now subject to general availability. I can only recommend that you Download and start using the tool today on your own systems (its agentless) – it analyses more than thousand different parameters also including Active Directory and Exchange clustering. Check out the blog at You had me at EHLO… for more information on this exciting “new” tool.