Wednesday, March 28, 2012

Useful Commands

Remove - Mcafee Anti-Virus File System Filter Driver
delete this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mfeavfk
disable IPV6 on windows 7 & windows 2008

reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255
Activate local administrator user on windows 7 & windows 2008
net user administrator /active:yes Pa55w0rd
Windows 7 local users profiles
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Windows Printer drivers
Increase concurrent user connections on windows 2008 powershell & exchange management console
winrm set winrm/config/winrs '@{MaxShellsPerUser="25"}'
winrm set winrm/config/winrs '@{MaxConcurrentUsers="25"}'
Get-ThrottlingPolicy | Set-ThrottlingPolicy -powershellmaxconcurrency 25
Copy NK2 files back to windows 7
WinSock Reset

 netsh   winsock   reset catalog           (resets winsock entries)
netsh    int    ip     reset c:\reset.txt   (resets TCP/IP stack)
Type "services.msc" in a command prompt find "SSDP Discovery" and set as "Automatic".
Thanks chev65 you are correct. I have finally found out the answer. If you are running Windows server 2008 R2 edition then you can find this policy in Group Policy editor and it will take effect for your Windows 7 machines. If not like me I am running Windows server 2008 standard then this is not an option within Group Policy editor on the server so must be done as a local policy change on the workstations.

You are right and it can be found in:-
Local Computer Policy
Administrative Templates
Network Connections
Do not show the "local access only" network icon
Select this to enabled.

Logoff and on and this will make the yellow exclamation icon disapear.
This is our fix for a corporate LAN with an Internet proxy server: -
Run “CMD” as Administrator, then enter
“Netsh winhttp import proxy source=ie”
What consistently worked for me is this:
1. Open network and sharing center
2. Click on the icon of your current connected network. It could be a house, bench, etc
3. Click on merge or delete network locations
4. At this time, disconnect from your network so you can delete all locations.
5. Delete all locations
6. Reconnect to your network again. You can either ignore homegroup by cancel or choose your preference.
7. You can now see that the disconnected issue has been resolved.
This has worked several times already for me and I just do it when the issue reappears. Typically, networks you’ve logged into from past connections are automatically stored here. When this gets to around 3 or more, thats when the error appears.
Im using a lenovo ideapad y460 with win 7 64 home premium os

Wednesday, March 21, 2012

Windows 7, Cannot open any hyperlink

(Open Command prompt as administrator on Windows Vista or Windows 7)

REG ADD HKEY_CURRENT_USER\Software\Classes\.htm /ve /d htmlfile /f
REG ADD HKEY_CURRENT_USER\Software\Classes\.html /ve /d htmlfile /f
REG ADD HKEY_CURRENT_USER\Software\Classes\.shtml /ve /d htmlfile /f
REG ADD HKEY_CURRENT_USER\Software\Classes\.xht /ve /d htmlfile /f
REG ADD HKEY_CURRENT_USER\Software\Classes\.xhtml /ve /d htmlfile /f
After this just make your Internet Explorer the Default browser.


Tuesday, March 13, 2012

The Dell - Microsoft Exchange 2010 Solution

Exchange 2010 - Under The Hood: What's changed?

  • By far the most important change with respect to Exchange Server 2007 is the new Database Availability Group. This will allow you to create multiple copies of an Exchange Server database within your organization, and you are no longer bound to a specific site (like in Exchange Server 2007), but can now stretch across multiple sites. Microsoft has also successfully transformed Cluster Continuous Replication and Stand-by Continuous Replication into a new ‘Continuous Availability’ technology.

  • While on the topic of simplifying, a lot of SysAdmins were having difficulties with the Windows Server fail-over clustering, so Microsoft has simply ‘removed’ this from the product. The components are still there, but they are now managed using the Exchange Management Console or Exchange Management Shell.

  • With the new Personal Archive ability, a user can now have a secondary mailbox, acting as a personal archive - this really is a .PST killer! You now have the ability to import all the users’ .PST files and store them in the Personal Archive, and using retention policies you can move data from the primary mailbox to the archive automatically, to keep the primary mailbox at an acceptable size, without any hassle.

  • To deal with ever-growing storage requirements, Microsoft also made considerable changes to the underlying database system. All you will need to store your database and log files with Exchange Server 2010 is a 2 TB SATA (or other Direct Attached Storage) disk. As long as you have multiple copies of the database, you’re safe! And the maximum supported database size? That has improved from 200 GB (in an Exchange Server 2007 CCR environment) to 2 TB (in a multiple database copy Exchange Server 2010 environment). If you haven’t yet considered what your business case will look like when upgrading to Exchange Server 2010, bear in mind that this will truly safe a tremendous amount of storage cost - and that’s not marketing talk!

  • Installing Exchange 2010 is not at all difficult, and configuring a Database Availability Group with multiple copies of the Mailbox Databases is just a click of the mouse (you only have to be a little careful when creating multi-site DAGs). Even installing Exchange Server 2010 into an existing Exchange Server 2003 or Exchange Server 2007 environment is not that hard! The only thing you have to be aware of is the additional namespace that shows up. Besides the standard namespace like and, a third namespace shows up in a coexistence environment: This is used when you have mailboxes still on the old (i.e. Exchange Server 2003 or Exchange Server 2007) platform in a mixed environment.

  • Lastly, for a die-hard GUI administrator it might be painful to start managing an Exchange environment with the Exchange Management Shell. Basic management can be done with the graphical Exchange Management Console, but you really do have to use the Shell for the nitty-gritty configuration. The Shell is remarkably powerful, and it takes quite some getting used to, but with it you can do fine-grained management, and even create reports using features like output-to-HTML or save-to-.CSV file. Very neat!

Quote of the Day