2097 Posted January 23, 2024 Posted January 23, 2024 Trying to solve this issue, but to no avail. We have setup device based subscription Office 365 activation, All machines are hybrid joined ( works fine and visable ) . We use Smoothwall as a proxy on port 3128 , and block port 80 and 443 for all users on our hardware firewall. Lets say i unblock port 80 & 443 at the hardware firewall , the machines activate office fine and it lasts 3 months . It them ports are blocked , it does not work/activate. I can see its not using the Internet proxy assigned by GPO/Per User, as it does not list any blocked URLs in the logs. I have installed Fiddler to catch all the urls going through port 80 , but they all say "200" which is strange . Found a previous article regarding .net framework 4 and editing the config file to include a proxy . ( unsure if this is still relevant ? ) Anyone done this recently with a similar setup that can help ? Thanks 2097
2097 Posted January 26, 2024 Author Posted January 26, 2024 Seem to have found some sort of solution ( well i know what can solve it , but doesnt explain much ). It does seem related to the WINHTTP proxy ( i have this set via registry / GPO ) If i manually run the command and set our proxy while the user is logged in with an elevated command prompt , it activates fine. So looks like it is using that ! .... Anyone got any ideas ?
2097 Posted January 27, 2024 Author Posted January 27, 2024 So after more testing and a sudden brain wave When you use cmd prompt on a 64bit OS WinHTTP puts the registry items in the WOW64 registry path I was setting the registry path via GPO to the non wow64 Reg path Now in the correct place Device based activation works great !
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now