http://www.windowsnetworking.com/articles_tutorials/Configuring-Volume-Folder-Quotas.html
Archive for the ‘Windows’ Category
February 19, 2010 by digg · Leave a Comment
Filed under: Windows
Social Tagging: quotas • windows 2003
Filed under: Windows
Social Tagging: quotas • windows 2003
Browse to this registry path on the target machine:
HKEY_LOCAL_MACHINE \ SOFTWARE\ Microsoft\ Windows NT \ CurrentVersion \ ProfileList
Now you have to identify the SID corresponding to the account you want to change the profile path.
1. Use this script
2. Use the Getsid tool from the Windows Server Resource Kit. (Read more here KB314843
Select the corresponding SID from the registry editor and change the ProfileImagePath value with the path you want to change to.
Restart your machinge and that’s all!
In IIS 6, when you configure the applications to work with integrated windows authentication, sometimes you get the following error:
HTTP Error 401.1 Unauthorized Access is denied due to invalid credentials
In order to solve this issue, proceed with the following:
- run cmd
- go to: C:\Inetpub\Adminscripts
- Check if NtAuthenticationProviders metabase property is set to NTLM
- Type: “cscript adsutil.vbs get w3svc/NTAuthenticationProviders” & enter
- If you get the message: “The parameter “ntauthenticationproviders” is not set at this node.” proceed
- Type: cscript adsutil.vbs set w3svc/NTAuthenticationProviders “NTLM” & enter
- A sample from a machine – click for larger
March 24, 2009 by redmad · Leave a Comment
Filed under: Windows
Social Tagging: CA • Certification Authority
Filed under: Windows
Social Tagging: CA • Certification Authority
When you setup the Certification Authority on a Windows server, a certificate for the CA is created, which will be expired after 5 years (default). You can extend the CA’s life beyond the end date of its original certificate. You can renew the CA with the following command:
certutil -renewCert ReuseKeys (renews the CA with the existing key pair)
or
certutil -renewCert (renews the CA with a new key pair)
Many users (using Windows 7 beta build 7000), reported a bug in Windows Media Player 12, which cause the corruption of MP3 files. Microsoft confirms this bug and releases an official patch for fixing this issue. With this update, Microsoft includes some instructions about installing Windows 7 beta. Basically they tell you to backup your mp3 files before installing Windows 7 beta and the install the KB961367 update (or make them read-only).
Follow these steps in order to uninstall and reinstall the Common Management Agent
- Run regedit
- Locate [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared Components\Framework]
- Locate Data Path and Installed Path and take a not of their data.
- Stop McAfee Framework Service
- Using the Installed Path, run the following
“C:\Program Files\Network Associates\Common Framework\FrmInst.exe” /forceuninstall
- Restart the system and confirm that the following has been deleted
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared Components\Framework]
- Confirm that the directories in the Installed Path and Data Path have been deleted.
Nou you can reinstall the Framework Service with the following command:
FramePkg.exe /Install=agent /ForceInstall
Note: Get the latest FramePkg.exe from your EPO server.
When you upgrade from a Windows Server 2003 R2 Standard SP2 to Windows Server 2003 R2 Enterprise Edition SP2 you may have a problem with memory. In case you have more than 4GB RAM on the machine (my situation was with 8GB) you have to do the following:
Locate boot.ini (it should be on the root of C:\ drive)
Under [operating systems] find the entry of Windows (it will be something like multi(0)disk(0)……=”Windows Server 2003, Enterprise” /noexecute=optout / fastdetect
and add
“/PAE” at the end
So now you will have
multi(0)disk(0)…..=”Windows Server 2003, Enterprise” /noexecute=optout /fastdetect /PAE
Restart the machine and now you ‘ll see the correct memory size.
February 3, 2009 by redmad · Leave a Comment
Filed under: Windows
Social Tagging: terminal services • windows 2000
Filed under: Windows
Social Tagging: terminal services • windows 2000
You are trying to connect on a Windows 2000 Standalone server and the terminal service ssessions are full.
- Connect to a machine on the same subnet of the target machine and make sure you have administrative privileges.
- Run cmd.exe
- Enter the following command: qwinsta /server:192.168.1.3 (IP address of the target server)
- The above will show you the users that hold the sessions of terminal services: (You will get a result like the following)
On this example the Administrator is connected from console and also holds another session of TS.
Also user1 is connected through TS.
In order to disconnect one of these users enter the following command:
rwinsta /server:192.168.1.3 3 (IP address of the target server and ID number)
This command will disconnect user user1.
January 29, 2009 by redmad · 1 Comment
Filed under: Windows
Social Tagging: device manager • driver problem in windows • uninstall device
Filed under: Windows
Social Tagging: device manager • driver problem in windows • uninstall device
We know that when you install a driver in Windows it remains there until you uninstall it. You can follow this procedure in order to uninstall drivers for hardware that no longer exists on the machine:
- open cmd
- run “set devmgr_show_nonpresent_devices=1″
- run “start devmgmt.msc”
- Click Show Hidden devices from the View menu
- You will now see all the installed drivers on your machine, even those that your system no longer uses them.
- You can now uninstall them.
January 28, 2009 by redmad · 3 Comments
Filed under: Windows
Social Tagging: automatic updates • SUS
Filed under: Windows
Social Tagging: automatic updates • SUS
By default when a pc / server connects to an SUS server, an susclientid is created on the pc / server. In case that you clone that pc / server, the same susclientid will exist on the cloned pc / server and the SUS server will only have one entry of this pc / server. In order to change it on the new pc / server you have to follow the following procedure:
- Stop Automatic Updates service
- run regedit and go to HLM/Software/Microsoft/Windows/CurrentVersion/WindowsUpdate
- on the right site of Registry Editor delete SusClientId and SusclientidValidation
- Start Automatic Updates service
- open cmd and run: wuauclt /detectnow
Now a new susclientid will be created on the machine and in a few seconds it will be created on the SUS machine.
Tested on Windows XP SP3 for the moment.
