What's up Chewy?

Updates from February, 2005 Toggle Comment Threads | Keyboard Shortcuts

• 

  Chewy Chong 2:27 am on February 28, 2005 Permalink | Reply  

  
  User Account Control BitMask Constants for C#

   

  I thought the following may be helpful for any C# endeavour with the manipulation of the userAccountControl attribute of an Active Directory User object.

   

  You can use Microsoft Identity Integration Server to provision a user based on certain events.  By specifying a userAccountControl value during the creation of an AD user, you can set certain attributes of the user account such as ‘Smartcard Required’ and ‘Do not expire password’.

   

  The userAccountControl value is of type LONG.  It acts as a bitmask.  You assign it in the following manner (OR-ing the constants):

   

  userAccountControlValue = DONT_EXPIRE_PASSWORD | NORMAL_ACCOUNT;

   

   

  Bitmask values:

   

  #region userAccountControl Constants

  const long SCRIPT = 0×0001;

  const long ACCOUNTDISABLE = 0×0002;

  const long HOMEDIR_REQUIRED = 0×0008;

  const long LOCKOUT = 0×0010;

  const long PASSWD_NOTREQD = 0×0020;

  const long PASSWD_CANT_CHANGE = 0×0040;

  const long ENCRYPTED_TEXT_PWD_ALLOWED = 0×0080;

  const long TEMP_DUPLICATE_ACCOUNT = 0×0100;

  const long NORMAL_ACCOUNT = 0×0200;

  const long INTERDOMAIN_TRUST_ACCOUNT = 0×0800;

  const long WORKSTATION_TRUST_ACCOUNT = 0×1000;

  const long SERVER_TRUST_ACCOUNT = 0×2000;

  const long DONT_EXPIRE_PASSWORD = 0×10000;

  const long MNS_LOGON_ACCOUNT = 0×20000;

  const long SMARTCARD_REQUIRED = 0×40000;

  const long TRUSTED_FOR_DELEGATION = 0×80000;
  

  const long NOT_DELEGATED = 0×100000;

  const long USE_DES_KEY_ONLY = 0×200000;

  const long DONT_REQ_PREAUTH = 0×400000;

  const long PASSWORD_EXPIRED = 0×800000;

  const long TRUSTED_TO_AUTH_FOR_DELEGATION = 0×1000000;

  #endregion

   

  More information can be found here:

   

  http://support.microsoft.com/default.aspx?scid=kb;en-us;Q305144

   

   

   

   

  Reply Cancel reply

  Required fields are marked *

  Name *

  Email *

  Website

  

  Notify me of follow-up comments via email.

  Notify me of site updates

• 

  Chewy Chong 10:39 am on February 26, 2005 Permalink | Reply  

  Talk: Realizing the Many Potentials of MIIS (Sydney – Thurs 3 Mar 2005) 

   

  As promised, here are the details on my preso at the Sydney Deep .NET User Group.  Thanks go out to Ken Schaefer (our resident IIS MVP) for introducing me to Nick Wienholt (SDNUG organizer) and to Nick who foolishly let me speak.

   

  Swing on by and listen to me blab.  I’ll try to dig up some t-shirts to give away.

   

  Thursday, 3 Mar 2005. 6.00pm – 8.00pm (Add to calendar)

   

  Realizing the Many Potentials of Microsoft Identity Integration Server by Chewy Chong

   

  This talk provides technical insight to the workings of MIIS and showcases business scenarios where MIIS (along with other solutions such as BizTalk) can offer a compelling solution.

   

  AMP Capital Investors, Ground Floor, 50 Bridge Street (The AMP Building), Sydney

   

  Pizza and drinks will be provided.

   

   
• 

  Chewy Chong 10:30 am on February 26, 2005 Permalink | Reply  

  Installation Tips When Using Domain Groups for a BizTalk Installation 

  I needed to use Domain Groups for a BizTalk installation on a domain controller (remember, no such thing as a local group on a DC).  You would also use Domain Groups for all clustering scenarios.

   

  There are a few things to note:

   

  1. The groups used by BizTalk have to be created in AD instead of locally.  I created a BizTalk OU just to hold these groups.
  2. The framework configuration tool does not create these for you.  You need to create them before starting the framework configuration.
  3. You reference these groups during the installation in the following manner “DOMAIN\BizTalk Administrator Group”.
  4. You need to add the administrator account being used for the installation to the necessary administrator groups.

   

  More details can be found here:

   

  http://msdn.microsoft.com/library/default.asp?url=/library/en-us/deploying/htm/ebiz_depl_config_swul.asp

   

   

   
• 

  Chewy Chong 10:14 am on February 26, 2005 Permalink | Reply  

  Failed to deploy BizTalk system assembly "…\Microsoft.BizTalk.DefaultPipelines.dll" 

  During the framework configuration portion of a BizTalk installation, I get the following error:

   

  Failed to deploy BizTalk system assembly “C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.DefaultPipelines.dll”

   

  I’m trying to put together a demo machine for an upcoming presentation where I have MIIS, BizTalk, VS.NET 2003, SQL 2000 installed on DC.  Hitting a few problems including this one.

   

  Some random named dll needs to be put in the %systemroot%\temp folder and referenced during the install.  This NETWORK SERVICE account needs full rights to this folder for the install.  You need to remove these rights after the install.

   

   
• 

  Chewy Chong 10:32 pm on February 1, 2005 Permalink | Reply  

  Clustering Two Windows 2003 Servers on Virtual Server 2005 

  A few years ago, I wrote a document on how to cluster two Windows 2000 machines on VMWare (this was before Microsoft Virtual PC).  Recently, I have been getting many requests on updating my document for Windows 2003 and Virtual Server 2005.  Lucky for me, the folks at Microsoft has a webcast on how to do exactly this.

   

  http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032267134&Culture=en-US