From Windows 2008 onward, that sorely missing functionality is available in the revamped dfsutil commandline tool. And as an added bonus, changing the TTL for a link is also possible.
Even more, dfsutil in 2008R2 (and therefore Windows 7 clients with RSAT installed) lets you set the Access Based Enumeration property.

Below are the property commands:

   1: E:\>dfsutil property

   2:  

   3: DESCRIPTION:

   4: Displays or modifies the properties of a folder target (link target) or

   5: namespace server (root target).

   6:  

   7: ------ PROPERTY Commands Supported ------

   8:  

   9: Sitecosting           Displays or modifies site costing for a namespace.

  10: RootScalability       Displays or modifies the namsespace polling mode.

  11: ABE                   Enable/Disable/View ABE property of a namespace.

  12: Insite                Displays or modifies the in-site property.

  13: TargetfailBack        Displays or modifies client fail back.

  14: SD                    Set/Get Security Information on the folder.

  15: State                 Displays or modifies a folder target or namespace server.

  16: TTL                   Displays or changes client referral caching.

  17: PriorityRank          Displays or changes the ordering method (priority rank).

  18: PriorityClass         Displays or changes the target priority.

  19: Comment               Sets or displays the comment for a namespace or link.

So, what do we do with this? Let’s say you’re migrating your DFS-Namespace enabled* Datashares to a newer fileserver with more storage capacity.

*no DFS-R , in case you’re wondering, because the original server might be a Windows 2003 non-R2 install.

A default link timeout is 7200 seconds or 2×60x 60 seconds = 2 hours, meaning your DFS client will check for changes in state after that time. During your migration window, you’ll want to ensure that any changes are picked up within a shorter time.

   1: E:\>dfsutil property ttl \\alt-92.net\data\share1

   2: The timeout for \\alt-92.net\data\share1 is 7200

First, we’ll change the timeout setting to a 5 minute setting:

   1: E:\>dfsutil property ttl set \\alt-92.net\data\share1 300

   2:  

   3: Done processing this command.

   4:  

   5: E:\>dfsutil property ttl \\alt-92.net\data\share1

   6: The timeout for \\alt-92.net\data\share1 is 300

Then, using both dfscmd and dfsutil, we’ll add our new fileshare to the link AND set it offline:

   1: dfscmd /add \\alt-92.net\data\share1 \\newserver\data\share1

   2: dfsutil property state offline \\alt-92.net\data\share1 \\newserver\data\share1

After syncing the content with robocopy (be sure to check the /MT switch for multithreading on Windows 2008R2 or Windows 7) we now flip the link state on both shares and restore the timeout value to its former setting:

   1: dfsutil property state offline \\alt-92.net\data\share1 \\oldserver\data\share1

   2: dfsutil property state online \\alt-92.net\data\share1 \\newserver\data\share1

   3: dfsutil property ttl set \\alt-92.net\data\share1 7200

After that, we’ll decommission the old fileserver, by taking the shares offline and removing the old links from the DFS Namespace with dfscmd:

   1: dfscmd /remove \\alt-92.net\data\share1 \\oldserver\data\share1

Et voila: we’ve migrated our DFS enabled fileshares to a new server with minimal downtime.

Fully scripted, its now feasible to migrate a DFS Namespace root with hundreds of links in just a few hours (including the final replication with robocopy – the bulk copy we’ve started a couple of days in advance) .

And as soon as that happens, Windows (Advanced) Firewall kicks into Public mode effectively locking your box down. Which is A Good Thing  – mostly, just not always what you want.

VMware KB article 1004813  also describes possible solutions to fix this. Aside from disabling the NICs (hey, we wanted to use those, remember?)  or changing the NICs over to Private Network (which you would have to do every reboot), you can configure the VMware adapters as so called Endpoint Devices per the procedure listed.
More information on the Endpoint device configuration is available on MSDN:
http://msdn.microsoft.com/en-us/library/bb201634.aspx
Reverting to the normal behaviour is as easy as flipping the DWORD to 0 or deleting the entry.

There is also a useful side effect to the *NdisDeviceType  setting:
Remote Desktop connections will keep working even with enabled virtual NICs, whereas by default Remote Desktop (TS) binds itself to all available network connections.

Which means I can finally RD into my desktop machine from my laptop with Host-Only and NAT adapters enabled to run a proper multi-machine, multi-network test.
Yay

[edit]

Link to KB article fixed 

The problem with Server Core … there’s no way for you to see the “updates to install” notice in the system tray when you log on to the computer because, well, there’s no systray!

In comes a handy piece of VBscript that allows you to do a manual quick check and start off the installation process, using the in-box Windows Update Agent API.
http://msdn.microsoft.com/en-us/library/aa387102(VS.85).aspx

Although the MSDN article states it does not run against SUS 1.0 servers, you don’t have to worry because both Windows Update (site) and WSUS 3.x employ the WUA API.

Save and run the script in the command prompt as “cscript ” since the default script host is graphical (wscript) on a Core box.

Set updateSession = CreateObject("Microsoft.Update.Session")
Set updateSearcher = updateSession.CreateupdateSearcher()
 
WScript.Echo "Searching for updates..." & vbCRLF
 
Set searchResult = _
updateSearcher.Search("IsInstalled=0 and Type='Software'")
 
WScript.Echo "List of applicable items on the machine:"
 
For I = 0 To searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    WScript.Echo I + 1 & "> " & update.Title
Next
 
If searchResult.Updates.Count = 0 Then
WScript.Echo "There are no applicable updates."
WScript.Quit
End If
 
WScript.Echo vbCRLF & "Creating collection of updates to download:"
 
Set updatesToDownload = CreateObject("Microsoft.Update.UpdateColl")
 
For I = 0 to searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    WScript.Echo I + 1 & "> adding: " & update.Title 
    updatesToDownload.Add(update)
Next
 
WScript.Echo vbCRLF & "Downloading updates..."
 
Set downloader = updateSession.CreateUpdateDownloader() 
downloader.Updates = updatesToDownload
downloader.Download()
 
WScript.Echo  vbCRLF & "List of downloaded updates:"
 
For I = 0 To searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    If update.IsDownloaded Then
       WScript.Echo I + 1 & "> " & update.Title 
    End If
Next
 
Set updatesToInstall = CreateObject("Microsoft.Update.UpdateColl")
 
WScript.Echo  vbCRLF & _
"Creating collection of downloaded updates to install:" 
 
For I = 0 To searchResult.Updates.Count-1
    set update = searchResult.Updates.Item(I)
    If update.IsDownloaded = true Then
       WScript.Echo I + 1 & "> adding:  " & update.Title 
       updatesToInstall.Add(update) 
    End If
Next
 
WScript.Echo  vbCRLF & "Would you like to install updates now? (Y/N)"
strInput = WScript.StdIn.Readline
WScript.Echo 
 
If (strInput = "N" or strInput = "n") Then 
WScript.Quit
ElseIf (strInput = "Y" or strInput = "y") Then
WScript.Echo "Installing updates..."
Set installer = updateSession.CreateUpdateInstaller()
installer.Updates = updatesToInstall
Set installationResult = installer.Install()
 
'Output results of install
WScript.Echo "Installation Result: " & _
installationResult.ResultCode 
WScript.Echo "Reboot Required: " & _ 
installationResult.RebootRequired & vbCRLF 
WScript.Echo "Listing of updates installed " & _
"and individual installation results:" 
 
For I = 0 to updatesToInstall.Count - 1
WScript.Echo I + 1 & "> " & _
updatesToInstall.Item(i).Title & _
": " & installationResult.GetUpdateResult(i).ResultCode 
Next
End If

Based on MSDN code sample from http://msdn.microsoft.com/en-us/library/bb524791(VS.85).aspx

#define UNICODE
#include <stdio.h>
#include <windows.h>
#include <lm.h>
#include <lmdfs.h>
 
void wmain(int argc, wchar_t *argv[ ])
{
   PDFS_INFO_4 pData;
   PDFS_STORAGE_INFO ps;
   DWORD er=0, tr=0, res, j;
 
   //
   // Check command line arguments.
   //
   if (argc<2)
      wprintf(L"Syntax: %s DfsEntryPath\n", argv[0]);
   else
   {
      //
      // Call the NetDfsGetInfo function, specifying level 4.
      //
      res = NetDfsGetInfo(argv[1], NULL, NULL,  4, (LPBYTE *) &pData);
      //
      // If the call succeeds, print the data.
      //
      if(res==0)
      {
 printf("Report for: %-30S\nStorages: %u\nComment: %S\n",pData->EntryPath, pData->NumberOfStorages, pData->Comment, pData->Timeout);
 printf("Timeout: %u\n",pData->Timeout);
 ps = pData->Storage;
         //
         // Loop through each target.
         //
         for(j=1;j<=pData->NumberOfStorages;j++)
         {
            //
            // Print the status (Offline/Online) and the name 
            // of each target referenced by the DFS link.
            //
 printf("Target %S  ", (ps->State == DFS_STORAGE_STATE_OFFLINE) ? TEXT("Offline:"): TEXT("Online :"));
            printf("\\\\%S\\%S\n",ps->ServerName,ps->ShareName);
            ps++;
         }
         //
         // Free the allocated memory.
         //
         NetApiBufferFree(pData);
      }
      else
         printf("Error: %u\n", res);
   }
   return;
}

It’s quick, it’s probably dirty, but it works just fine (and no admin privileges needed as it does the same as your average DFS client code).

Sample output:

D:\>dfsquery \\alt-92.net\files\0054
Report for: \\ALT-92\files\0054
Storages: 2
Comment:Department 54 data store
Timeout: 300
Target Online : \\ENDEAVOUR\data\0054
Target Offline: \\Equinoxe\data\0054

It shows timeout value, comments (description field in DFS console) the number of link targets and their individual link state.

Vista does not have this feature, but there is a workaround available. Installing the VHDMount utility from Virtual Server 2005R2 SP1 lets you use the VHD storage driver and the vhdmount utility.

1. Download the Virtual Server 2005 R2 SP1 setup from http://www.microsoft.com/windowsserversystem/virtualserver/downloads.aspx .
2. Run setup and choose Custom Setup type:

   
   

3. Verify the default selection for VHD Mount is marked:

   

   Click Next to install and finish the setup.

   

4. You can use the command line vhdmount utility to attach a .VHD file, or alternatively, use these registry entries to create a context menu for the four actions.

   Windows Registry Editor Version 5.00
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD]
   @="Virtual Machine Hard Drive Image"
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\DefaultIcon]
   @="C:\\Program Files\\Microsoft Virtual PC\\Virtual PC.exe,-327"
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell]
   @="Mount"
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Commit]
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Commit\command]
   @="\"C:\\Program Files\\Microsoft Virtual Server\\Vhdmount\\vhdmount.exe\" /c \"%1\""
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Discard]
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Discard\command]
   @="\"C:\\Program Files\\Microsoft Virtual Server\\Vhdmount\\vhdmount.exe\" /d \"%1\""
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Dismount]
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Dismount\command]
   @="\"C:\\Program Files\\Microsoft Virtual Server\\Vhdmount\\vhdmount.exe\" /u /d \"%1\""
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Mount]
    
   [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Virtual.Machine.HD\shell\Mount\command]
   @="\"C:\\Program Files\\Microsoft Virtual Server\\Vhdmount\\vhdmount.exe\" /p \"%1\""

   The result is a context menu on right-clicking a .VHD file like this.

   

   Mounting your disk file is now as easy as a right-click away, and the VHD will show up as a new disk in Explorer.

[update] The offer period has expired and new entries are no longer available.
Normal subscriptions are of course still possible .

Just klick http://technet.microsoft.com/nl-nl/dd491981.aspx and enter your data, wait a couple of days for confirmation and you’ll get access to all the latest and greatest Server operating systems & software.

Prices are 370 € (ex VAT/BTW) for a full year, renewals are 270 € (ex VAT/BTW).
Technet Plus Direct means online access to the software library (download only – no CD shipments), two support calls (worth 299 €) and free e-learning courses.

For a list of available software, See the complete list on the TechNet Plus Subscriptions home page.

The script:

On Error Resume Next
Const HARD_DISK = 3
Const adOpenStatic = 3
Const adLockOptimistic = 3
 
strNamespace = "root\cimv2"
strDomain = "domain"
 
strDate = FormatDateTime(Now(), 2)
strTime = FormatDateTime(Now(), 4)
Set objNetwork = CreateObject("Wscript.Network")
' =====================================================================
arrComputers = Array("Server1","Server2","Server3")
 
For Each strComputer In arrComputers
Set objWMIService = GetObject("winmgmts:" & strComputer & "root\CIMV2")
Set colDisks = objWMIService.ExecQuery _
("SELECT * FROM Win32_LogicalDisk Where DriveType = " & HARD_DISK & "",,48)
 
Set objConnection = CreateObject("ADODB.Connection")
Set objRecordSet = CreateObject("ADODB.Recordset")
 
objConnection.Open _
"Provider = Microsoft.Jet.OLEDB.4.0; " & _
"Data Source = c:\scripts\diskspace_database.mdb"
 
objRecordSet.Open "SELECT * FROM tbldiskspace" , _
objConnection, adOpenStatic, adLockOptimistic
For Each objDisk in colDisks
objRecordSet.AddNew
 
objRecordSet("server") = strComputer
objRecordSet("domain") = strDomain
objRecordSet("disk") = objDisk.VolumeName
objRecordSet("drive") = objDisk.DeviceID
objRecordSet("totalspace") = round(objDisk.Size /1024/1024,2)
objRecordSet("freespace") = round(objDisk.FreeSpace /1024/1024,2)
objRecordSet("percentage") = (objDisk.Freespace /objDisk.Size)*100
objRecordSet("date") = strDate
objRecordSet("time") = strTime
 
objRecordSet.Update
 
Next
Next
 
objRecordSet.Close
objConnection.Close
' =====================================================================

Access DB has a simple table layout, and a couple of queries and comboboxes.
Table:

Form:

Using the queries and by generating a PivotTable view, it’s easy to spot growth trends on disks.
Graph showing available free space:

It looks like a ‘nice to have’ feature for the ubertweaker and enthusiast at first, but think about this:

What if you need to support a DTA environment for desktops? Now, you don’t have to mess around with Virtualization software – just provision and deploy the VHD file with the appropriate configuration (such as a segmented VLAN for Test or Dev) and let your application developers use the same hardware.
No double PCs, no double network outlets, no extra poweroutlets or powerconsumption (think green here).

Sure, it needs some tweaking (preventing disk access between images) but.. tempting nonetheless…

http://blogs.msdn.com/ts/archive/2008/08/07/smart-sizing-the-ts-client.aspx

Since the Windows XP timeframe, the TS Client has had the ability to run in “smart-sized” mode (users of Remote Assistance will be familiar with this mode). Smart-sized mode means that the entire remote desktop is always visible in the client window, with no scrollbars being necessary. In effect, for the same size client window, smart-sizing shows you more graphic data, while a non-smart-sized client window has to use scrollbars and shows much less.

Which means by adding

smart sizing:i:1

to a .rdp file (which is a textfile after all) you can get resizing Remote desktop windows too

Spiegelbeeld 6001.18000 (x86 en x64 voor Venster Server 2008 en Vergezicht SP1) Standalone Downloaden

Spiegelbeeld zit te troepenleiding- wachtrij werktuig welk in staat stellen origineel werktuig vervaardiger (OEMs), vroedschap en Venster enthousiast voor inneming, voor wijzigen, en voor toepassen vijl- op basis van schijf spiegelbeeld voor stroomversnelling deployment. Spiegelbeeld werken van Venster spiegelbeeld (.wim) archief en annuleerteken werkzaamheden van andere technologisch welk toepassing .wim spiegelbeeld, zulke zoals Venster Instelling, Venster Deployment Diensten ( venster DS), en naar de Systematiek Regie Server (SMS) Besturingssysteem Wezenstrek Deployment Troep.

Spiegelbeeld zit plain tweedehands voor omgaan met en schipperen Venster instelling installatie schijf spiegelbeeld vijl tevredenheid, zulke omtrentslipstream Venster Vergezicht SP1 stap troep te RTM voorstelling van Venster Vergezicht spiegelbeeld. Spiegelbeeld komt zonder kosten vanVenster Automatiseren Installatie Kit ( venster AIK of WAIK). Naar de WAIK voorstelling 6001.18000 ( of 6.0.6001.18000) is vrijgekomen met het oogmerk barkas van Venster Server 2008 en Venster Vergezicht SP1.

WAIK zit te downloaden van ruim 1 GB, en vergen verbruiker voor brandwond naar de ISO spiegelbeeld voor schijf. Wanneer u vergen uitsluitend Spiegelbeeld, ketterij’ naar de uittreksel Spiegelbeeld voorstelling 6001.18000 voor 32- stukje (x86) en 64- stukje (amd64 of x64) Venster. Te naar de RAR samenpersen archief omvat naar de overeenkomstig voorstelling vanVsp1cln.exe, naar de werktuig voor schoonmaak en wegnemen backup-kopie RTM voorstelling van archief over installeren Stap Troep 1.

Downloaden Spiegelbeeld voor 32- stukje Venster: ImageX_x86.rar
Downloaden Spiegelbeeld voor 64- stukje Venster: ImageX_x64.rar

Beider archieven inhouden imagex.exe, intlcfg.exe, vsp1cln.exe, wimfltr.inf, wimfltr.sys, en wimgapi.dll.

voornaam: You’re voorlezing te toestel vertalen pagina wie zit voorzien ” zoals zit” zonder waarborg. Ongelikt menselijk vertaling, toestel vertaling doet niet verstaan naar de spraakleer, semantiek, zinsleer, taaleigen van natuurlijke taal, zus vaak voedingsmiddelen onnauwkeurig en loeien kwaliteit tekst wie zit illusoir en onbegrijpelijk. Zus, wees zo goed verwijzen voororigineel Engels stuk wanneer ter twijfeling.

If you got this far, my hat’s off to you.

The original text reads:

ImageX 6001.18000 (x86 and x64 for Windows Server 2008 and Vista SP1) Standalone Download

ImageX is a command-line tool that enables original equipment manufacturers (OEMs), corporations and Windows enthusiasts to capture, to modify, and to apply file-based disk images for rapid deployment. ImageX works with Windows image (.wim) files and can work with other technologies that use .wim images, such as Windows Setup, Windows Deployment Services (Windows DS), and the System Management Server (SMS) Operating System Feature Deployment Pack.

ImageX is commonly used to manipulate and manage Windows setup installation disc image file content, such as to slipstream Windows Vista SP1 service pack into RTM version of Windows Vista image. ImageX comes free with Windows Automated Installation Kit (Windows AIK or WAIK). The WAIK version 6001.18000 (or 6.0.6001.18000) is released with the launch of Windows Server 2008 and Windows Vista SP1.

WAIK is a download of more than 1 GB, and requires user to burn the ISO image to disc. If you require only ImageX, here’s the extracted ImageX version 6001.18000 for 32-bit (x86) and 64-bit (amd64 or x64) Windows. Within the RAR compressed archive includes the corresponding version of Vsp1cln.exe, the tool to clean up and remove backup RTM version of files after installing Service Pack 1.

Download ImageX for 32-bit Windows: ImageX_x86.rar
Download ImageX for 64-bit Windows: ImageX_x64.rar

Both archives contain imagex.exe, intlcfg.exe, vsp1cln.exe, wimfltr.inf, wimfltr.sys, and wimgapi.dll.