I see two possibilitiles ... well - three, but two are variations on the same theme.
Option 1 - make sure you have WWW-access.
=> If you have physical control over your OSD'ing machines (i.e. clients get OSD'ed in a particular physical area), you can either have them work around the Proxy you have, which would resolve the issue.
=> Not sure how well this is doable, but the "variation on the theme" would be to try and feed Windows 7 the proxy information. That would need to be researched and I am not sure it's possible, but that's the other variation on the theme, if you can't work around the proxy.
Option 2 - Don't use the WWW.
=> You can set up an activation server for WIndows OS's inside your network (so you don't need to go on to the WWW) to activate them (you'd need to read up on this from the Microsoft pages - I had to look up something related when Win 7 initially came up for my labs). This is a possibility, as the Server itself sits in your network (thus no WWW-access needed), and it's the server that's talking to Microsoft as it needs, rather than the client.
For that option, this should help you along:
- Paul Hoffmann
LANDesk EMEA Technical Lead
Dont forget that you need 25 activations, before you really can use KMS.
1 of 1 people found this helpful
if you are set on using a MAK key and must go through your proxy, you can add URLs to the Proxy Authentication exclusion lists.
Excerpt from the Volume License Deployment Guide - http://technet.microsoft.com/en-us/library/dd772269.aspx
Activating MAK Clients Through a Proxy Server
Activation over the Internet may be blocked if the proxy server requires user authentication. In Microsoft Internet Security and Acceleration (ISA) Server, this setting is called Basic Authentication. Because activation requests do not present the user's credentials to the proxy server, Microsoft recommends not using Basic Authentication with ISA Server or other proxy servers. However, if Basic Authentication or a comparable mechanism must be used on the proxy server, add the following URLs to the Proxy Authentication exclusion list:
Many thanks for all the answers.
In an amazing coincidence, I was in a meeting yesterday where it came to life that when this all goes live we will have a working KMS server just for this , so - problem solved.