Additional Feature Requests

Marduk · 2011-08-26 17:46

In an effort to streamline the number of scripts I have to run when switching profiles, I'd like to add two feature requests:

1. Ability to specify DNS Suffixes and orders to append (which is different from just specifing a single DNS Suffix). In Win7 at least, this setting is stored in the registry key:

HKLM\System\CurrentControlSet\Services\TCPIP\Parameters

in the REG_SZ value "SearchList"

2. Ability to switch Outlook profiles when switching profiles. The default Outlook profile is stored in the registry also in this key:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

in the REG_SZ value "DefaultProfile"

while the profile names can be found by iterating through the subkeys of HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

Happy to provide more info if needed!

And thanks for listening...

Dan

NetSetMan Support · 2011-08-27 00:18

I understand that there are always custom needs that are not present in NSM. Both the suggested features have never been requested before so I'm curious to hear the use cases that make changing thoses settings regularily necessary.

For now I'll put both on the request list but I assume both features to be very special needs while there are many other new more popular features waiting to be implemented before that.

I guess you'd be better off sticking to scripts that will do the job for you for now.

Marduk · 2011-08-27 00:48

Thanks for the reply and I completely understand your need to priorize your time and feature requests based on popular demand. Just consider these my votes for what I would like to see added. As you stated, all the tasks can be accomplished with scripts so I'm happy, just always trying to look for ways to further streamline my process. I also realize that adding a feature to support multiple OSes and configurations makes things a lot harder than just running a script which is configured for my environment.

I'd be surprised if others don't need the same features though. My scenario is the corporate consultant scenario where I work at multiple client sites with different network and mail requirements for each customer, so switching these items happens daily for me. Then again, maybe my scenario is more unique than I think smile .

If anyone else has the same, um "requirements", I'd be happy to post my scripts since together with that awesome NetSetMan program, I have the operation down to just the few clicks it takes to kick off the profile change.

NetSetMan Support · 2011-08-27 16:37

Since I don't use those configurations myself and nobody else requested them, yet, I'd like to ask you whether you could rescribe your use case in detail. e.g. why is there any need in changing the DNS suffix/domain at all and why do you need more than one setting?
If I can understand the need in it it's more likely to find its way into NSM.

I see two options in the official dialog in Windows for the DNS suffix issue. One allows a list ("Append these DNS suffixes (in order)") and one a single entry ("DNS suffix for this connection").
If you needed one DNS suffix only, would it make any difference to you if this entry would show up in the list or in the text box?
If the list is used, is the text box still required?

Marduk · 2011-10-11 15:11

Sorry for taking so long to get back to you, but I was in the process of moving and just started catching up again...

My exact situation is I am a consultant in IT that works with a lot of different customers. Many of the offices I work in (I have quite a few profiles) use a DNS suffix (or suffixes) to correctly route their links as the actual link itself does not have the full suffix in it. This allows shorter links in e-mail and web sites.

for example companies will send me a link:

http://ProdSharePoint/home.aspx

instead of

http:// ProdSharePoint.eastcoast.reallybigcorp.com/home.aspx

If I don't have the company specific domain in the DNS list, a browser will try and resolve the link to the internet, which will not be availible. Therefore I need to append these suffixes whenever I visit a customer site and get on their network. I use the workaround script described in my second post to add the DNSes so that the links will resolve. This relates to the "Append these DNS suffixes (in order) list on the advanced network configuration tab. Resolution is attempted by the suffixes in this list before trying the suffix in the "DNS suffix for this connection" text box. Both are actually used and could be useful. This MS article here (http://technet.microsoft.com/en-us/libr … 59339.aspx) explains it better than I just did.

Some companies even have multiple domains:

https://InternalApp1.amer.reallybigcorp.com/start.aspx
https://InternalApp2.emea.reallybigcorp.com/start.aspx
https://InternalApp3.apac.reallybigcorp.com/start.aspx
https://GlobalApp.reallybigcorp.com/start.aspx

Which is why I need more than one suffix.

Outlook profiles are the based on a similar need. When I switch "companies" I also usually need to switch e-mail servers in order to receive e-mail on their systems. Having more than one Outlook profile is the easiest way to handle it and setting when switchin profies (currently via my script) means I don't have to select an Outlook profile at Outlook startup.

Anyway, I hope this explains at least my need of why such settings would be useful and hope this can make it in to a subsequent release of this very useful product.

Dan

NetSetMan Support · 2011-10-21 01:59

Thanks for your detailed description. This helps understanding the use case. I'll use your information as soon as I get to rework this issue.

NetSetMan Support

#1 2011-08-26 17:46

Additional Feature Requests

#2 2011-08-27 00:18

Re: Additional Feature Requests

#3 2011-08-27 00:48

Re: Additional Feature Requests

#4 2011-08-27 16:37

Re: Additional Feature Requests

#5 2011-10-11 15:11

Re: Additional Feature Requests

#6 2011-10-21 01:59

Re: Additional Feature Requests