Luckily I still had the proxycfg output file from running the wsus reporting
tool during the support incident, so I was able to get the original
post-project server 2003 install proxy settings, which are:
Current WinHTTP proxy settings under:
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Proxy Server(s) : https://<projectserver name>;http://<projectserver
name>
Bypass List : <local>;<root url of top-level wss site>;<server name
of wss server, probably taken from root url of admin site>;<root url of PWA
site>
I then ran your suggested command, substituting my values:
PROXYCFG.EXE -d -p "https://<projectserver name>;HREF="http://<projectserver
name>" CLASS="WNAnc" TARGET="winout">http://<projectserver name>" "
<local>;<root url of top-level wss site>;>;<server name of wss server,
probably taken from root url of admin site>;<root url of PWA
site>;*.microsoft.com"
my settings after this command:
Current WinHTTP proxy settings under
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Flags = PROXY_TYPE_DIRECT | PROXY_TYPE_PROXY
Proxy Server = https://<projectserver name>;HREF=http://<projectserver
name> CLASS=WNAnc TARGET=winout>http://<projectserver name>
Bypass List = <local>;>;<root url of top-level wss site>;>;<server name
of wss server, probably taken from root url of admin site>;<root url of PWA
site>;*.microsoft.com
Now, PWA can connect to my wss server, and I can update my project server at
update.microsoft.com.
My only concern now is the difference between the original post-project
server install proxy settings for "proxy server(s)":
Proxy Server(s) : https://<projectserver name>;http://<projectserver name>
And my current settings for "proxy server(s):
Proxy Server = https://<projectserver name>;HREF=http://<projectserver name>
CLASS=WNAnc TARGET=winout>http://<projectserver name>
Should I be concerned about this? Everything seems to work, but the original
settings seem less complex.
If I wanted to revert to:
Proxy Server(s) : https://<projectserver name>;http://<projectserver name>
what is the command syntax?
--
Berry Morgan
JSO
Berry at JSO said:
I don't have a proxy server on my network, so I'm not sure how to proceed
with your instructions.
The Project Server 2003 install did put some (probably default) proxy
settings on the server initially, and I don't remember what they were (I
didn't specify any proxy settings during my project server installation), but
those settings were removed during a service call with Microsoft Support
concerning the failure of windows updates.
Any ideas on the default proxy settings that Project Server 2003 puts on the
server (whether you want them or not)?
Maybe if I can reapply those settings I can hit wss again.
--
Berry Morgan
JSO
Rolly Perreaux said:
Hi Berry,
Try this:
1. From the Project Server, click Start --> Run
Type CMD and click OK.
3. At the command line and type the following command:
PROXYCFG.exe
This command displays the current settings
Also write down the settings as you may need them (just in case)
4. Then type the following command:
PROXYCFG.exe -d
This command will clear the settings
5. Then type the following command:
net stop wuauserv
This command will stop the Automated Updates services
6. Then type the following command:
net start wuauserv
This command will start the Automated Updates services
7. Then type the following command:
PROXYCFG.exe -d -p <URL of project server> <bypass-list>
The bypass list will include the computer name and fully qualified
domain name of the Project Server
If you have multiple proxy server names (which you should) use double
quotes and semicolon to separate the servernames. For example on my
server I typed:
PROXYCFG.exe -d -p "
https://PSDEMO;http://PSDEMO"
"<local>;psdemo;psdemo.adatum.com;*.microsoft.com"
NOTE: command is all on one continuous line and there must be a space
between [-p <server-name> [<bypass-list>]
For example: ...
http://PSDEMO" "<local>;...
And I also added *.microsoft.com to the bypass list so that I wouldn't
create problems accessing the Microsoft Update website to get the latest
server and application updates.
8. From PWA, click on a link to the SharePoint Project Workplace site to
see if you can access.
Let us know if this works...
I removed the proxy settings on my project 2003 server in order to get
windows update to function properly, but now my project 2003 server cannot
connect to my wss server.
How can I manually use the proxycfg utility to reset my proxy settings?
And will I have to remove my proxy settings, run windows update, then reset
my proxy settings every time to get windows updates?
TIA
--
Rolly Perreaux, PMP, MCSE
Project Server Trainer/Consultant
TriMagna Corporation
Microsoft Gold Partner
http://www.trimagna.com
