Windows 7 may be Microsoft’s most anticipated product ever. It builds on Windows Vista’s positives, and eliminates many of that OS’s negatives. It adds new functionality, too—all in a package that is less resource-hungry than its predecessor.
And whether or not you're upgrading from Vista or skipping it altogether and moving up from Windows XP, you'll need to know how to make the most of it in your environment. Here are 77 tips and tricks to get you there.
Windows 7: 77 Windows 7 Tips
There have been reports of a problem when running Refresh, Replace, Sysprep and Capture, and Custom task sequences with MDT 2010. When running those scenarios an error message is displayed after completing the wizard that states “A connection to the distribution share could not be made”. When looking at the log files the error states: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.”
This problem seems to occur most often when logged onto the client machine as one user and entering different credentials into the deployment wizard or customsettings.ini.
We have developed a fix for this problem. To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder. Open the file in notepad and replace the following code in the MapNetworkDriveEX function:
Microsoft Deployment Toolkit Team Blog : Fix for ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed” problem with MDT 2010
I concocted this batch file script a couple weeks ago to determine where a client was accessing the network from and then mapping shares accordingly. In this instance, folks were logging in through either Citrix of the local LAN. If they were logging on by way of the LAN, the DFS shares needed to be mapped. If logging on through Citrix, they needed to log on directly to the shares, instead of the DFS replicas.
I did this based on the IP address of the Gateway obtained through the connection. As you can see the Gateway changed based on the location, so it was easy to determine where they client was logging in from. There’s also another section in the script so that a VPN or “other” connection can be added to the logic, too.
To use the script just spot the IP Gateway address fields (XXX for one Gateway, YYY for the other) and modify based on the IP Gateway addresses assigned in your organization.
rem Subnets for reference
rem Citrix Gateway: XXX.XXX.XXX.XXX
rem Server Gateway: YYY.YYY.YYY.YYY
rem Grab IP address and dump to a file
echo Checking for your location
rem Seaching for default gateway in IP dump above
findstr "XXX.XXX.XXX.XXX" "%userprofile%\ipconfig.txt"
if not errorlevel 1 goto Citrix
echo Not Citrix
findstr "YYY.YYY.YYY.YYY" "%userprofile%\ipconfig.txt"
if not errorlevel 1 goto Server
echo not Server
net use G: \\server\share
net use P: \\server\share
net use Z: \\server\share
net time \\timeserver /set /y
net use G: \\DFS_ROOT\share
Net use P: \\DFS_ROOT\share
net use Z: \\DFS_ROOT\share
net time \\timeserver /set /y
rem Other settings (for VPN etc)
rem more commands
Modena was put together by a team of people developing solutions for Microsoft's own internal IT group. They have made the tools available as-is on the Connect website for others to use as they wish (with no support or any plans for ongoing updates – as soon as MS IT is happy with them they're done). We are having some discussions with the team to see how we can integrate these tools into MDT, but there are no definitive plans at this point.
[mssms] Modena – deploying drivers through WSUS – SMS-ConfigMgr Email Discussion List Archive
PEIMG failed to use the servicing stack shim library (ssshim.dll) to locate a servicing stack that matches the target image (0×901f0005).
Error Creating MDT Boot Image « The Realm of the Verbal Processor
There are a few operations in the MDT 2010 Deployment Workbench that can take a while. We’ve done our best to optimize those processes, but in many cases they will still take a good amount of time to complete. While you could certainly start an operation in one Deployment Workbench and then open another Deployment Workbench so that you can continue working, it would be even better to schedule these long-running tasks so that they run automatically, ideally when you are sleeping and when there aren’t any active Lite Touch deployments going on.
Michael Niehaus' Windows and Office deployment ramblings : Automating Long-Running MDT 2010 Tasks
Windows Live Messenger mandatory upgrade will patch development code vulnerability
Microsoft: Upgrade Messenger or else
System Center Essentials provides several ways to remotely manage computers, including:
- Computer Management MMC
- Remote Desktop
- Remote Assistance
- Tasks to show current information, such as process usage
Sometimes though what is wanted is just a remote command window without the overhead of opening a full remote desktop session.
The PsExec tool which is one of the SysInternals tools provides a way to open a remote command window without needing to install anything on the remote computer.
System Center Essentials Team Blog : Using psExec to Open a Remote Command Window