TechNet Top Questions - January 2001

Article
02/09/2009

Exchange 5.5 and ADSI

Q: Mark Fenwick from the U.K. wrote:

Hi,

Does anyone have any experience of generating an exchange mailbox programmatically in Visual Basic? I have found all the information I can on doing it via DAPI but all the examples are written in C and so do not provide any constant value declaration, they also do not cover mailbox creation directly.

We have a tool that we use to add new users to the Windows NT domain, create their home folder with the correct permissions and add them to the company database. We now need this program to create a new mailbox as well. Can anyone help me?

Thanks

A: Rich Matheisen hit it out of the park with:

Think "ADSI". There are examples in the ADSI SDK and in several books from WROX Press.

Rich Matheisen
MCSE+I, Exchange MVP

Rich may have been referring to the example "Creating a Mailbox with IADsSecurityDescriptor and IADsSID in the ADSI Resource Kit."

The ADSI SDK can be downloaded from https://www.microsoft.com/ntserver/nts/downloads/other/ADSI25/sdk.asp

Holidays, It's All in Your Outlook

Q: My company is looking for a way to put our holiday schedule (not just the recognized holidays) into everyone's Outlook Calendar. Is there a way to do this without having everyone manually put in the dates themselves? I know how to add the holidays through the Tools>Options menu, but want to make it so that our users don't have to each do that; and also so that we can put the extra days in that our company has off.

Any help is appreciated.

Thanks,

Elizabeth

elizabethj@datachannel.com

A: And Sue replied:

See https://www.slipstick.com/dev/olforms/holiday.htm for a little custom form that lets you send the holidays around to everyone. All the user has to do is click one button.

Sue Mosher

Author of:
"Teach Yourself Microsoft Outlook 2000 Programming in 24 Hours"
"Microsoft Outlook 2000 E-mail and Fax Guide"

Outlook and Exchange solutions at https://www.slipstick.com/

Windows 2000 Terminal Services, May I See Your License?

Q: Hello

Could someone please help me with a terminal services licensing issue. I am using Windows 2000 server terminal services. I have a 5 CAL license for terminal server for 4 clients. For some reason one of the users had been issued with a temporary license that has just expired. I would have expected that once the temporary liecense expired that the user would be assigned to a permanent license. However, this has not been the case. The event manager indicates that his existing temporary license has expired (event 1004: The terminal server cannot issue a client license) and that the client had been disconnected because its temporary license has expired (event 1011: The terminal services client ASA has been disconnected because its temporary license has expired)

It also states that no further license can be issued (event1004: The terminal server cannot issue a client license)

Upon investigation of the Terminal Services Licensing manager, I see that all 5 CAL licenses have been issued out. I recognize three clients that the licenses have been issue to but two licenses have been issued to a client called DEFAULT. I don't know who Default is.

I would like to remove this licensing from default so that the client who previously had the temporary license can have a permanent license.

Thank you in advance for your assistance.

Regards

David Soong

A: David,

Unfortunately there is no easy solution to your issue. Please see the following Knowledge Base article for details:

258045 - Terminal Services Licensing Does Not Accept a Valid License Key Pack

Also, please refer to the MS Windows 2000 Terminal Services Licensing white paper at:

https://www.microsoft.com/technet/prodtechnol/win2kts/evaluate/tslicen.mspx

SMS 2.0 SP2 and Windows 2000 Professional Clients

Q: We have a small single 2.0 sp2 site with multiple subnet Windows NT 4.0 Servers as CAPs and Logon Points. Windows Logon discovery smsls has worked effectively for Win95/98 clients. When Win2K Pro clients were introduced the logon discovery does not work unless File and Print Sharing is enabled on the Win2K Pro client.

Ccm.log reported the client configuration manager service was unable to connect to admin$ on the W2K Pro client machines during client installation.

Enabling File and Print Sharing seemed to correct this.

Is there some cleaner way to empower logon discovery without enabling File and Print Sharing on Win2K Pro clients?

Any suggestions?

Thanks in advance.

Steve

A: Seam M. Loftus had a prompt reply:

Make sure there is a client connection account on all your local machines with administrative access (unless your lucky enough to remember what the account name and password was for the original one) and specify it in your new SMS sites Connection Accounts folder.

Good guess Seam, but while it is a great idea and a recommended practice to always create a backup client connection account, this account is used for the Client to talk to the CAP and not vice versa. You can't set this locally on computers, this is set from the site.

The problem seems to be that the CCM (client configuration manager) won't connect to W2k professional clients. CCM will attempt to connect to these clients when a local client install has "failed" (this is normal) because the local user isn't a local admin. So CCM comes in with administrative rights (using the SMSService account, or an optional SMS Remote Installation account) and installs the client services and registry entries that the local user could not.

It is not clear how file and printer sharing should affect this with W2k clients. CCM simply connects to the admin$ and driverletter$ shares on the client. Have these been removed? File and printer sharing IS necessary for Network Discovery on win9x clients, perhaps this is what is being discussed and not Logon Discovery?

Our recommendation would be to review the CCM.LOG to see what is really going on here.

Windows 2000 Professional and Personal Web Server

Q: Hi –

I am on a workstation with Windows 2000 Professional installed, and need to get Personal Web Server set up in order to run Cold Fusion. It was a no brainer with Win 98, but I'm having fits with Win 2000. The MS site sends me to the IE 5 page, and other Web references are broken. OK, so I must've fallen asleep somewhere along the way, so I don't know what happened to it. I did download the IE upgrade, but it didn't seem to help matters. My FrontPage 2000 book said it's on the Win 2000 Server CD, so I did the 'install add-ons' and found a similar beast, but again it didn't seem to help much.

Can someone tell me what happened to PWS, where I can get it, or how I can get a personal web server (or any variety) going so that Cold Fusion will have what it wants?

Many thanks.

Mary

A: Hey Mary-

Things have changed a little bit on Windows 2000 Professional. Go into Control Panel, then Administrative Tools, followed by Personal Web Manager. I think this is the interface you are more use to.

If you don't see it, go back into Control Panel, select Add/Remove Programs, then Windows Components and click Internet Information Services (IIS) (18 meg). Follow the install instructions.

This new Web server can do some pretty cool things, but I am not sure if CFM will work with it or not. Would you let me know if you do get it to work with IIS5.0?

HTH-

doug

Office 2000 Temporary Files

Q: Gordon Betts asked:

Could anyone who has a few spare moments see if their networked computers produce tmp files on bootup in the Windows temp folder.

Mine produces two on each networked computer each of zero bytes and I would like to find out if it is only mine that do it.

Thanks for your help.

Gordon

A: After quite a thread, Gordon found his own answer:

Thank you all for your help. It is Office 2000 files causing the tmp files. Mdm.exe to be accurate and the registry has to be altered to get rid of them. See 221438 - OFF2000: Files Whose Name Begins with "fff" Appear in Windows Folder