Justin's Tech Blog

To switch the specified adapter from a static address to DHCP, type the following command: netsh interface ip set address "Local Area Connection" dhcp NOTE: Typing this command changes the interface named "Local Area Connection" to DHCP. To display all of the adapters in the computer with their current IP addresses to determine the correct adapter name, type the following command: Netsh interface ip show config To change to a static address, type the following command: netsh interface ip set address "Local Area Connection" static ipaddr subnetmask gateway metric NOTE: Replace ipaddr with the static IP address, subnetmask with the subnet mask, gateway with the default gateway and, if necessary, metric with the appropriate metric. The following example changes the interface "Local Area Connection" to a static address of 192.168.0.10 with a subnet mask of 255.255.255.0, and the interface has a default gateway of 192.168.0.1 with a metric of ...

I was troubleshooting to fix above error and below article helped me to fix it easily:) http://blogs.technet.com/b/scvmm/archive/2010/05/10/understanding-network-location-and-tags-in-scvmm.aspx

To resolve this problem, uninstall the ghosted network adapter from the registry using one of the following methods: Back to the top Method 1 Click Start, click Run, type cmd.exe, and then press ENTER. Type set devmgr_show_nonpresent_devices=1, and then press ENTER. Type Start DEVMGMT.MSC, and then press ENTER. Click View, and then click Show Hidden Devices. Expand the Network Adapters tree. Right-click the dimmed network adapter, and then click Uninstall. Back to the top Method 2 The DevCon utility is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, disable, restart, update, remove, and query individual devices or groups of devices. To use DevCon, follow these steps: Download the DevCon tool by clicking the following article number to view the article in the Microsoft Knowledge Base: 311272 (http://support.microsoft.com/kb/311272/ ) The DevCon command-line utility functions as an alternative to Device Manager Unp...

How to slipstream Service Pack 3 into Microsoft Office Project 2003 These instructions apply to Project 2003 Standard Edition. To slipstream other versions, you’ll need to replace PRJSTDE.MSI with the name of the MSI for your Project Edition. Steps You’ll need a Volume Licence Key setup CD. D:\setup.exe /aSave to C:\project2003\ Download Project 2003 SP3 Extract its contents to C:\Project2003SP3\ with: Project2003SP3-KB923622-FullFile-ENU.exe /Q /C /T:C:\Project2003SP3\Perform slipstream with: msiexec /p C:\Project2003SP3\PROJECTSP3.msp /a C:\Project2003\PRJSTDE.MSI SHORTFILENAMES=TRUE /qbDelete the C:\Project2003SP3\ folder as you no longer need it

Patching an administrative installation point You must install administrative updates (MSP files) from the command line. On the command line, you run Windows Installer with options to specify the path to the MSI file and the name and path of the MSP file. The MSI file is the Windows Installer package file from your original administrative image. The MSP file is the Office administrative update file that contains information about the changes in the upgrade. The update instructs Windows Installer to add, update, or remove files in the administrative image. -------------------------------------------------------------------------------- Note Before you update an administrative installation point, make sure that no clients are using the share. If a file on the share is in use during the upgrade process, a newer version of that file is not copied to the administrative installation point. -------------------------------------------------------------------------------- To apply an update ...

Office System (2003) SP3 Slipstreaming by Daniel Petri - January 8, 2009 Printer Friendly Version How can I slipstream service packs into Office System (2003)? Like in previous versions of Office and their corresponding Service Packs, SP3 can be slipstreamed into an administrative installation point of Office 2003, in order to allow for a fully integrated installation. This scenario explains how to create an integrated installation of Office System (2003) and the corresponding service pack in a shared distribution folder on a network or on your local computer. To complete this procedure, you must have the original Office 2003 CD media. Note: This explanation is based upon usage of Office System (2003) and SP3, but will also work for any future service packs. For Office XP integrated installations see "Office XP SP1/2/3 Slipstreaming". Prerequisites for slipstreaming Before we begin anything, you'll need to have a few things: 1.Office System (2003) CD 2.You will need the A...

Managing Message Tracking Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2009-06-03 A message tracking log is a detailed log of all message activity as messages are transferred to and from a computer that is running Microsoft Exchange Server 2007 and that has the Hub Transport server role, the Mailbox server role, or the Edge Transport server role installed. Exchange servers that have the Client Access server role or Unified Messaging server role installed don't have message tracking logs. You use message tracking logs for message forensics, mail flow analysis, reporting, and troubleshooting. You can use the Set-TransportServer cmdlet for all message tracking configuration tasks on a Hub Transport server or Edge Transport server. You can use the Set-MailboxServer cmdlet for all message tracking configuration tasks on a Mailbox server. For servers that have the Hub Transport server role and the...