Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –

 

·    Open Registry editor by typingregedit in Run prompt

·    Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA

·    Select the DisplayName to modify, and remove the leading characters from the value data up to the last "%;" i.e.

o    For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”

o    For x64, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to "Cisco Systems VPN Adapter for 64-bit Windows”

·    Try connecting again

 

Please do revert back if this solution does not work.

Great article on what is involved in moving the IIS root folder in Server 2008 and newer OSs.

 

Having your content on a different partition than your Operating System is a good security practice. In previous IIS versions is was possible to do this during setup time in an unattend file. Due to changes in Vista and Windows Server 2008 setup it became impossible to do that however. After setup the IIS7 INETPUB directory will be on the same partition as Windows. Moving the INETPUB directory to a different drive has to be done after setup completes. Here is a table of configuration entries that use the INETPUB directory on a default install. An example in the right column shows how to move the setting to a different drive using the APPCMD command-line tool. Once all the settings are moved the only step left is to copy the INETPUB directory via XCOPY. Here is a link to a batch file (packaged up in MOVEIIS7ROOT.ZIP) that moves the INETPUB directory to a drive of your choice.

Directory	Config setting location	Example how to move setting to a different drive (this example uses the F:\ drive)
LOGS\FREBLOGS	Failed Request Event Buffering (FREB) is a new IIS7 feature that logs failed requests. The default path for FREB logs is %systemdrive%\inetpub\logs\FailedReqLogfiles.	%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/sites -siteDefaults.traceFailedRequestsLogging.directory:"F:\inetpub\logs\FailedReqLogFiles"
LOGS\LOGFILES	The default path for IIS7 log files is %systemdrive%\inetpub\logs\logfiles.	%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/sites -siteDefaults.logfile.directory:"F:\inetpub\logs\logfiles"%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/log -centralBinaryLogFile.directory:"F:\inetpub\logs\logfiles"%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/log -centralW3CLogFile.directory:"F:\inetpub\logs\logfiles"
TEMP\APPPOOLS	AppPool isolation is a new feature in IIS7. A dedicated AppPool configuration file gets automatically created before a new Application Pool is started. The default location of these files is %systemdrive%\inetpub\temp\appPools	reg add HKLM\System\CurrentControlSet\Services\WAS\Parameters /v ConfigIsolationPath /t REG_SZ /d f:\inetpub\temp\appPools
HISTORY	Configuration history ensures that changes can be rolled back. The default location for configuration history is %systemdrive%\inetpub\history	%windir%\system32\inetsrv\appcmd set config -section:system.applicationhost/configHistory -path:f:\inetpub\history
TEMP\ASP COMPILED TEMPLATES	Classic ASP stores compiled ASP code on disk if more than 250 compiled templates are in memory. The default disk cache location is "%systemdrive%\inetpub\temp\ASP Compiled Templates"	%windir%\system32\inetsrv\appcmd set config -section:system.webServer/asp -cache.disktemplateCacheDirectory:"f:\inetpub\temp\ASP Compiled Templates"
TEMP\IIS TEMPORARY COMPRESSED FILES	IIS7 will cache compressed responses on disk if necessary. The default location for the compression cache is "%systemdrive%\inetpub\temp\IIS Temporary Compressed Files"	%windir%\system32\inetsrv\appcmd set config -section:system.webServer/httpCompression -directory:"f:\inetpub\temp\IIS Temporary Compressed Files"
WWWROOT	IIS7 comes with a Default Web Site which points to %systemdrive%\inetpub\wwwroot.	%windir%\system32\inetsrv\appcmd set vdir "Default Web Site/" -physicalPath:f:\inetpub\wwwroot
CUSTERR	IIS7 stores Custom Error Pages in %systemdrive%\inetpub\custerr	%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='401'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='403'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='404'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='405'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='406'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='412'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='500'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='501'].prefixLanguageFilePath:f:\inetpub\custerr%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='502'].prefixLanguageFilePath:f:\inetpub\custerr
WWWROOT and FTPROOT Locations	Service Packs and other installers need to know where your WWWROOT and FTPROOT directory is. That's why the location is also specified in the registry.	reg add HKLM\Software\Microsoft\inetstp /v PathWWWRoot /t REG_SZ /d f:\inetpub\wwwroot reg add HKLM\Software\Microsoft\inetstp /v PathFTPRoot /t REG_SZ /d f:\inetpub\ftproot

 

MOVING THE CONTENT:

Once the configuration is changed you have to copy all content from your root drive to your new drive including ACLs and empty directories:

Example:

                    xcopy c:\inetpub f:\inetpub /E /O /I

 

/E copies all directories even if they are empty
/O copies all security settings, i.e. Access Control Lists on files and directories
/I assumes the destination is a directory

PLEASE BE AWARE OF THE FOLLOWING:
WINDOWS SERVICING EVENTS (I.E. HOTFIXES AND SERVICE PACKS) WOULD STILL REPLACE FILES IN THE ORIGINAL DIRECTORIES. THE LIKELIHOOD THAT FILES IN THE INETPUB DIRECTORIES HAVE
TO BE REPLACED BY SERVICING IS LOW BUT FOR THIS REASON DELETING THE ORIGINAL DIRECTORIES IS NOT POSSIBLE.

Local copy of download

moveiis7root.zip (1.66 kb)

With the existance of UAC in the windows world, I find my self looking for easier ways to run a command as administrator (usually via command line) without needing to turn off UAC.

Here are some useful links that helped me solve this very issue

Elevation Power Toys

http://technet.microsoft.com/en-us/magazine/2008.06.elevation.aspx  (note, you also need to sysinternals suite installed in "%ProgramFiles%\Sysinternal Suite"

Elevate Utility

http://code.kliu.org/misc/elevate/

Sudo for windows

http://sourceforge.net/projects/sudowin/

http://marcvaneijk.wordpress.com/2010/06/12/sharepoint-2010-and-adfs-2-0-the-complete-step-by-step-guide/

http://malcolmplested.blogspot.com/2011/06/setting-up-adfs-with-office-365.html

FreeCommanderis an easy-to-use alternative to the standard windows file manager. The program helps you with daily work in Windows. Here you can find all the necessary functions to manage your data stock. You can take FreeCommander anywhere - just copy the installation directory on a CD or USB-Stick - and you can even work with this program on a foreign computer.

FuturixImager is a compact and customizable image viewer. It is capable of opening more then 40 file types, including all most popular ones (GIF, JPEG, PNG, TIFF, JPEG2000, raw, DNG).

Texter saves you countless keystrokes by replacing abbreviations with commonly used phrases you define. Unlike software-specific text replacement features, Texter runs in the Windows system tray and works in any application you're typing in. Texter can also set return-to markers for your cursor and insert clipboard contents into your replacement text, in addition to more advanced keyboard macros.

Stickies is a PC utility was written to try to cut down on the number of yellow notes I was leaving stuck to my monitor. It is a computerised version of those notes. The design goal behind Stickies is that the program is small and simple. Stickies will not mess with your system files, or write to the registry. Stickies stores information in a single text-based ini file. 

ShellRunAs is a command-line tool call Runas that is handy for launching programs under different accounts, but it’s not convenient if you’re a heavy Explorer user. ShellRunas provides functionality similar to that of Runas to launch programs as a different user via a convenient shell context-menu entry. Read more..

Command Prompt Here tool

http://support.microsoft.com/kb/269155

1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
3. Type Start DEVMGMT.MSC, and then press ENTER.
4. Click View, and then click Show Hidden Devices.
5. Expand the Network Adapters tree.
6. Right-click the dimmed network adapter, and then click Uninstall.

This is a copy from here....

This freeware application is a System Tray utility for providing quick access to common IIS tasks which are useful on a SharePoint development box. It may also be useful to others working with IIS. In essence, it enumerates the app pools on your box and lets you right click 'em to bounce 'em!

If you are experiencing problems with APM, please see the FAQ.

 

---

Version 3.0.0.0 (7th December 2009)

SharePoint 2010 and IIS7 only

removal of IIS6 legacy code 
addition of new SP2010 services 
SharePoint to IIS App Pool name mapping

Download 
Application Pool Manager 3.0.0.0.

 

---

Version 2.0.0.0 (27th November 2008)

Complete rewrite 
Vastly reduced working set 
Full Vista support 
UAC manifest 
IIS status detection 
IIS6 operations use legacy APIs 
IIS7 operations use Microsoft.Web.Administration 
Event Logging

Download 
Application Pool Manager 2.0.0.0.

 

---

Version 1.1.0.0 (23rd May 2008)

 

New Options Layout 
Form does not show on start up 
Warm Up and IISReset now run in the background 
Option to hide Tool Tips 
Ability to hide Application Pools 
Restart WSS Timer & WSS Admin Services 
STSADM now works on localised versions of Windows Server 
Ability to exclude STSADM from Warm Up 
PID displayed on context menu for spun up Application Pools 
Version Check

Download 
Application Pool Manager 1.1.0.0.

 

---

Version 1.0.3.0 (10th August 2007)

Added Tooltip to display Process ID if an app pool has spun up. Refreshes in event of recycle. 
Does not depend upon iisapp.vbs

Windows 2008/Vista Support: Requires Legacy IIS WMI.

Download 
Application Pool Manager 1.0.3.0.

 

---

Version 1.0.2.0 (14th April 2007) 

Added Support for Windows Vista. 
Added ability to refresh the list of Application Pools. 
Removed dependency upon the "Warm Up" scripts. 
Added ability to "warm up" multiple URLs. 
Improved notifications. 
Removed 'Recycle' tooltip which caused artifacts on Virtual Machines. 
Improved keyboard navigation.

 

System Requirements 
Windows Server 2003 Service Pack 1 or later, or Windows Vista. 
Internet Information Services 6.0 or 7.0 (with IIS6 Management Compatability installed). 
.NET Framework 2.0.

Download 
Application Pool Manager 1.0.2.0.

Instructions for post event warm ups: 
Enter the full URLs (including http:// , /default.aspx or /pages/default.aspx etc) in comma seperated format. Warm ups do not support HTTP 302s. There is no need to install the Warm Up scripts with this version. If you are upgrading from the previous version, remove the Path within applicationpoolmanager.config, this is no longer required.

 

---

Version 1.0.1.0 
Added Event Notifications. 
Added ability to perform an IISReset. 
Added ability to perform post event "Warm Ups".

System Requirements 
Windows Server 2003 Service Pack 1 or later. 
Internet Information Services 6.0 
.NET Framework 2.0

Download 
Application Pool Manager 1.0.1.0

 

Instructions for configuring post event "Warm Ups".

This requires the Warm Up Scripts posted by Joel Oleson. Download the ZIP file and extract the contents to a folder on your local disk (e.g. c:\warmup).

1. Within the Options dialog of Application Pool Manager, select the Enable Post Events Warm Up check box.
2. In the Path to WarmUpServer.cmd text box, enter the path you extracted the scripts to. 
   Note: do not include a trailing slash, or the filename itself.
3. In the URL to Warm Up text box, enter the hostname you wish to warm up. 
   Note: do not include http:// or a trailing slash.
4. Click OK to save the configuration. The configuration is persisted in the ApplicationPoolManager.config file.

Following a IISReset or Application Pool Recycle event, WarmUpServer.cmd will be run, and you will receive notifications of it's progress:

  

Note that the file startup.bat is redundant and not required. STSADM is run to warm up the admin interfaces by Application Pool Manager. Also there will be a delay whilst the HTTP GETs performed by WarmUpServer are executed before the final notification is displayed.

Don't forget to modify the WarmUpServer.cmd file to reference correct URLs for your SharePoint Central Administration and Shared Services Provider Administration web sites.

 

 

What might get done in the next version.

•  
  • Allow associations between Application Pools and Warm Up Hosts. 
    e.g SharePoint Intranet App Pool when recycled warms up http://intranet/ but 
    SharePoint WCM App Pool when recycled warms up http://wcm/
  • Removal of initial display of About/Options form (if I can figure out how to do that).
  • Activate via keyboard shortcut (if I can figure out how to do that).
  • Add keyboard shortcuts for each Application Pool displayed.
  • Add ability to hide Application Pools (e.g. SharePoint Central Administration v3).
  • Add Start and Stop operations.

If you have feature requests, please leave a comment here. No promises!!

Acronis True Image (http://www.acronis.com)

DriveImage XML (http://www.runtime.org/driveimage-xml.htm)

After getting Windows 7 x64 installed, I was having a problem getting a few gadgets to work correctly (like the Pandora Gadget). It turns out this gadget uses Flash, which only comes in a 32 bit version. The Sidebar is x64, and can't access Flash. Since there is no x64 version of flash (come on Adobe -- its time to bite the bullet!!), I started digging around for a way to overcome this limitation -- as luck would have it, Microsoft ships the 32-bit version of the side bar in the x64 versions.  Now all I needed to do was get it to startup instead of the default x64 bit version.

Edit the following Registry Key:
\\HKCU\Software\Microsoft\Windows\CurrentVersion\Run\SideBar

Change the key to this: C:\Program Files (x86)\Windows Sidebar\sidebar.exe /autoRun

(The only addition is loading sidebar.exe from c:\program files (x86)\ instead of c:\program files\)

This should get you by until Adobe gets their act together!

Resizing a VHD drive is not particularly complicated, it just involves a number of steps.

To Shrink

1. Mount the VHD in Windows 7/2008 using Disk Management Tools (or DISKPART)
2. Defragment the drive, makeing sure the free space is also defragmented (UltraDefrg in Optimize mode is a good free tools for this)
3. Resize the main parition using Disk Management Tools (or DISKPART)
4. Unmount the VHD Drive
5. Resize the actual VHD file (VHDResizer is a great tool for this)
   1. http://sysadmingeek.com/articles/how-to-resize-a-microsoft-virtual-hard-drive-vhd-file/

To Expand

Resize the actual VHD file (VHDResizer is a great tool for this)

1. http://sysadmingeek.com/articles/how-to-resize-a-microsoft-virtual-hard-drive-vhd-file/
2. Mount the VHD in Windows 7/2008 using Disk Management Tools (or DISKPART)
3. Defragment the drive, makeing sure the free space is also defragmented (UltraDefrg in Optimize mode is a good free tools for this)
4. Resize the main parition using Disk Management Tools (or DISKPART)
5. Unmount the VHD Drive