In order to prepare your mobile device for Active Server Synchronization you have to check if your mobile device operating system is able to use this feature. Generally all mobile devices running Windows Pocket PC Edition 2003 or Windows Pocket PC Mobile 2003 are prepared to work properly. In addition other devices may run without any problems if they run a version of Microsoft Active Sync 3.7.1 or higher. The download can be found at :
After a successful implementation of Microsoft Exchange Server 2003, the next step would be implementing lots of improvements within the working processes of the company and its organizational infrastructure. Many companies are willing to plan their company resources using Exchange and Outlook to make it easier for each employee to find out if a resource is already booked or still available.
These resources could be conferencing rooms, cars, projector, etc. – in general nearly everything that is being used by more than one employee during working days.
With an Exchange / Outlook infrastructure in your company there are various ways to make this work. Within this article we will have a close look at each possibility. We will not just talk of how to configure it, in addition, we will discuss the pros and cons of these implementation tasks.
In the previous article we took our ChangeIPAddress.vbs script developed earlier and modified it to use it to change the IP address on a remote computer. Here's what our modified script looked like:
Option Explicit Dim objWMIService Dim objNetAdapter Dim strComputer Dim strAddress Dim arrIPAddress Dim arrSubnetMask Dim colNetAdapters Dim errEnableStatic
If WScript.Arguments.Count = 0 Then Wscript.Echo "Usage: ChangeIPAddress.vbs new_IP_address" WScript.Quit End If
strComputer = "xp2" strAddress = Wscript.Arguments.Item(0) arrIPAddress = Array(strAddress) arrSubnetMask = Array("255.255.255.0") Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Set colNetAdapters = objWMIService.ExecQuery("Select * from Win32_NetworkAdapterConfiguration where IPEnabled=TRUE") For Each objNetAdapter in colNetAdapters errEnableStatic = objNetAdapter.EnableStatic(arrIPAddress, arrSubnetMask) Next
The line:
strComputer = "xp2"
tells us that the computer targeted by the script has the name XP2. The remote computer XP2 initially had an IP address of 172.16.11.43.
Let's go back to the script ChangeIPAddress.vbs that we developed to change the IP address of a network adapter:
Option Explicit Dim objWMIService Dim objNetAdapter Dim strComputer Dim strAddress Dim arrIPAddress Dim arrSubnetMask Dim colNetAdapters Dim errEnableStatic
If WScript.Arguments.Count = 0 Then Wscript.Echo "Usage: ChangeIPAddress.vbs new_IP_address" WScript.Quit End If
strComputer = "." strAddress = Wscript.Arguments.Item(0) arrIPAddress = Array(strAddress) arrSubnetMask = Array("255.255.255.0") Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Set colNetAdapters = objWMIService.ExecQuery("Select * from Win32_NetworkAdapterConfiguration where IPEnabled=TRUE") For Each objNetAdapter in colNetAdapters errEnableStatic = objNetAdapter.EnableStatic(arrIPAddress, arrSubnetMask) Next
In the previous article in this series we started exploring what we could do with the Win32_NetworkAdapterConfiguration class. This powerful WMI class has 61 properties and 41 methods that can be used for retrieving and changing TCP/IP networking settings on Windows computers.
To illustrate the power of this class, we took the sample script we developed in the first and second articles and, using information about this class on MSDN, we customized our original script to make it do something different. Specifically, we took a script that changed the IP address of a network adapter and customized it to come up with a new script that disables NetBIOS over TCP/IP (NetBT) on all network adapters that have TCP/IP bound and enabled on them.
We need to explore this powerful WMI class further, and we're going to do so in several future articles. But before we do this, let's talk about The Hump.