Posts Tagged ‘Server 2003’

Adding stsadm to path for easy access on MOSS 2007

October 7th, 2011

On your MOSS 2007/WSS 3 server you will probably want to add the following to your path variable in order to access the stsadm command without having to navigate into that folder.

1 – right click on computer and go to properties.  
2- For Server 2008 choose advanced system settings.
3 -For Server 2003 & 2008 choose Advanced
4 – Click Environment Variables.
5- Under System Variables find “PATH” and click edit
6- go to the end of the string, add a semi-colon and then copy and paste the following in: c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin 
7 – save out.  Now when you open the command prompt, you just have to type stsadm to get to your command.



Tags: , ,
Posted in Uncategorized | Comments (0)

Removing Persistent Proxy Settings

September 13th, 2011

Problem

Removing Persistent Proxy Settings
Keywords: Windows 7 Proxy, Windows Vista Proxy, IE Proxy Clear Proxy Settings from Windows

Platform

Windows 7, VISTA, XP, Server 2008, 2003

Symptoms

Your organization had a proxy server that was subsequently retired. You go into internet explorer and remove the proxy settings. You also check all group policy settings and everywhere else, but cannot find it setup anywhere. However, your computer is still directing traffic to the old proxy.

Fix

This seemed like it would be a fairly straight forward fix, but ended up taking a lot of searching to find the simple answers.

To View the current proxy settings:
For Win Vista/7 from the command line: netsh winhttp show proxy
For Windows XP from the command line: proxycfg

To reset the current proxy settings:
For Win Vista/7 from the command line: netsh winhttp reset proxy
For Windows XP from the command line: proxycfg /d

I ended up putting the following into a batch file and deployed it via group policy to all of my domain computers to get rid of the proxy settings. The batch file would disable the proxy, clear the IE cache (to get rid of the proxy.pac remnants), and then flush the dns cache.

Commands to copy/paste into .bat file for Win 7:
netsh winhttp reset proxy
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
ipconfig /flushdns

Tags: , , , , ,
Posted in Uncategorized | Comments (2)

Reduce RAS initial DHCP Reservations

October 19th, 2010

Problem

I have a subnet that is running out of IP addresses.  RAS is taking up 10 ip addresses on the DHCP server even though I only have a small handful of users that will likely use the server at once. I wanted to reduce the number of IP’s initially reserved by RAS. 
Keywords: routing and remote access reduce dhcp reservations vpn.

Platform

Windows Server 2008 R2 standard. Also works on Server 2003 and likely Small Business Server 2003/2008

Symptoms

When looking on the DHCP Server there are 10 leases allocated to the VPN server.  

Fix

To reduce the number of initial leases/reservations that RAS takes you just have to change and/or create the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters\IP
Value Name: InitialAddressPoolSize
Data Type: REG_DWORD
Default: 10
The default is 10 leases, I wanted it at 3 so I just added the key above and set the key to 3.  This means that it will only take 3 IP addresses initially, if those are used it will request an additional 3 leases.

Tags: , , , ,
Posted in Uncategorized | Comments (0)

WSUS 2.0 and WSUS 3.0 Crash Consistently

March 29th, 2007

Problem

WSUS 2.0 and WSUS 3.0 Crash Consistently
Keywords: Winodws Server Update Services 2 or 3, Windows Software Update Services, WSUS, WSUS 2, WSUS 3, WSUS Self-Update , WSUS SimpleAuth Web Service, WSUS Client Web Service

Platform

Windows Server 2003 current service pack and all patches

Symptoms

After installing WSUS 2.0 or 3.0 the service seems to work for a short period of time and then “hang”. If you restart IIS and the Update Service it will allow clients to connect to WSUS for another short period of time. In your application event logs you get the following Errors:

WSUS 3.0

Event 12002 The Reporting Web Service is not working.
Event 12032 The Server Synchronization Web Service is not working.
Event 12022 The Client Web Service is not working.
Event 12042 The SimpleAuth Web Service is not working.
Event 12052 The DSS Authentication Web Service is not working.
Event 13042 Self-update is not working.

WSUS 2.0
Event 506 The SelfUpdate Tree is not working. Clients may not be able to update to the latest WUA client software and communicate with the WSUS Server.

Additionally if you look in your security event logs you will see the following:

Failure Audit | Security | Logon/Logoff | Event ID 534 | User : System |

Logon Failure:
Reason: The user has not been granted the requested
logon type at this machine
User Name: IUSR_YOURMACHINENAME
Domain: YOURDOMAIN
Logon Type: 8
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: YOURDOMAIN
Caller User Name: NETWORK SERVICE
Caller Domain: NT AUTHORITY
Caller Logon ID: (0x0,0x3E4)
Caller Process ID: 1612

Fix

If you problem is exactly as described above then the problem is that NETWORK SERVICE does not have the rights to log on as a service in the comptuers Local Security Policy.
To fix this you will need to determine if the group policy is being set at the domain level or at the machine level. The easiest way to do this is to do the following:

1. Open the control panel
2. Open Administrative Tools
3. Execute “Local Security Policy”
4. Navigate to: Local Policies -> User Rights Assignment -> Log on as a service
5. Double-click “Log on as a service” to open its properties
6. Is NETWORK SERVICE listed? If yes this solution will not fix your problem. If no continue.
7. You will want to click “Add User or Group” and then type Network Service. It would be good if you also added ASPNET if it is missing.
8. If “Add User or Group” is greyed out, this is because the policy is being set through the domain and is being inherited. You will want to use Active Directory Users and Computers or Group Policy Management to edit the policy that your server is inheriting this from.
9. After you add NETWORK SERVICE, you should reboot the computer and everything should work. When you reboot go back in and verify that NETWORK SERVICE is sitll in there.

Note: NETWORK SERVICE also should be delegated the right “Replace a process level token”.

Tags: , ,
Posted in Uncategorized | Comments (0)

Windows Update Error number: 0x8024400A

January 17th, 2007

Problem

Windows Update Error number: 0x8024400A
Keywords:

Platform

Windows Server 2003 Standard Edition, SP1

Symptoms

Windows update would not run and the computer would not send a status report to a WSUS server. When Visiting Windows Update to get updates manually it would give the following page/error:

[Error number: 0x8024400A]
Windows Update has encountered an error and cannot display the requested page. You may find the following resources helpful in resolving the problem:

Fix

I found a resource that solved my problem:

From the command prompt:
regsvr32 MSXML3.DLL

Then go into services and restart the Automatic Updates service.

After Automatic Updates successfully restarts open IE and try windows updates again.

Other wsus problems:

WU client failed Searching for update with error 0x80244010

Solution: Clear all browser history, including cookes, temporary internet files, forms, etc.

Also, Found an article that said there is a percentage of comptuers ~20% that there is an unknown error with clients scanning into the wsus server due to compression on IIS 6.0 ‘s part. Error WU client failed Searching for update with error 0x8024400a is thrown in the c:\windows\windowsupdate.log file. If you go to c:\windows\system32\inetsrv on the WSUS server and rename the suscomp.dll to suscomp.dll.old, then restart IIS clients will randomly start scanning in.

If none of that works try each of these from the command prompt and restart :

regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wups2.dll
regsvr32 wuweb.dll

Still not working?

Stop the Automatic Updates Service
Delete the folder c:\windows\SoftwareDistribution
rename the windows update log: c:\windows\windowsupdate.log to windowsupdate.log.old
Start the Automatic Updates Service
Go to a command prompt and type: wuauclt /detectnow

Tags: ,
Posted in Uncategorized | Comments (0)