Limitations of Policy Documents, Roaming and administration prefs

I am having some issues with Policy documents and wonder if anyone knows of ways to achieve these things or if there are plans to address them? It’s a little tiny rant too.

Registration Settings:

Cannot specify a default cluster server to create a mail file on. (Cannot specify to create a cluster mail file)

Cannot specify to create a cluster replica of the roaming directory either.

Cannot specify a format for the shortname.

The “Group Assignments” field errors with : “The specified database lookup generated more than 65000 bytes of results…”. We have 4602 Groups (admittedly they do require a cleanup…but we’ve just merged domains)

Desktop Settings:

Why can’t I enable/disable specific ports. We only want to use TCPIP. Currently the options are to compress or not to compress. But I’m stuck with LAN0, Com1, SPX…Any way to set clients up so these ports aren’t enabled?

I haven’t had a chance to play with the rest of the policy docs…so I’ll stop there. These policy documents look great. They’re making administration a whole lot easier but they’re still not quite there.

If you ask me, most (or all) of the registration options should be mirrored in the registration settings policy document. Actually, some of them are missing from the Administration Preferences default options as well which is a bit disappointing.

Roaming:

Has anyone noticed that if you set up a new user with a roaming profile, you can specify to create replica’s of the roaming profile on the cluster member? But if you upgrade a user to roaming you can’t specify this? You have to create the replicas manually!

Oh, The ‘store ID in Address book’ option is only available when setting up a roaming user. You cannot change this option without turning off roaming and re-setting it up for a user.

OK I’m finished my rant now. Are any of these issues earmarked for future releases?