SCCM V4 Document

http://msaadexpert.googlepages.com/SCCM_NativeMode.pdf

 

-------------------
Thanks,

Jonathan Swift  - "May you live every day of your life."

MP Error "Failed to get WebDAV settings on the machine (0x80070003)" in Windows 2008

 

 

 

<01-05-2010 08:48:45>         ======== Completed Installion of Pre Reqs for Role SMSMP ========
<01-05-2010 08:48:45> Installing the SMSMP
<01-05-2010 08:48:45> Passed OS version check.
<01-05-2010 08:48:45> IIS Service is installed.
<01-05-2010 08:48:45> checking WebDAV configuraitons
<01-05-2010 08:48:45> Failed to get WebDAV settings on the machine (0x80070003)
<01-05-2010 08:48:53> ====================================================================

 

Resolution

To install and configure WebDAV for IIS 7.0 to support management point and BITS-enabled distribution point site system computers

1. Depending on your server operating system platform, download either the x86 or x64 version of WebDAV from: http://go.microsoft.com/fwlink/?LinkId=108052.

2. Depending on which version was downloaded, run either the webdav_x86_rtw.msi or the webdav_x64_rtw.msi file to install WebDAV IIS 7.0 extensions.

3. Enable WebDAV and create an Authoring Rule, as follows:

   1. Navigate to Start / All Programs / Administrative Tools / Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager. In Server Manager, select the Features node, and click Add Features to start the Add Features Wizard.
      
   2. In the Connections pane, expand the Sites node in the navigation tree, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system.
      
   3. In the Features View, double-click WebDAV Authoring Rules.
      
   4. When the WebDAV Authoring Rules page is displayed, in the Actions pane, click Enable WebDAV.
      
   5. After WebDAV has been enabled, in the Actions pane, click Add Authoring Rule.
      
   6. In the Add Authoring Rule dialog box, under Allow access to, click All content.
      
   7. Under Allow access to this content to, click All users.
      
   8. Under Permissions, click Read, and then click OK.
      

4. Change the property behavior as follows:

   1. In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings.
      
   2. In the WebDAV Settings page, under Property Behavior, set Allow anonymous property queries to True.
      
   3. Set Allow Custom Properties to False.
      
   4. Set Allow property queries with infinite depth to True.
      
   5. If this is a BITS-enabled distribution point, under WebDAV Behavior, set Allow hidden files to be listed to True.
      
   6. In the Action pane, click Apply.
      

5. Close Internet Information Services (IIS) Manager.

To add Remote Differential Compression for site server and branch distribution point computers

In Server Manager, on the Features node, click Add Features to start the Add Features Wizard.

1. On the Select Features page, select Remote Differential Compression, and then click Next.

2. Complete the rest of the wizard.

3. Close Server Manager.

 

=====================================================================================

 

Issue 2:

 

 

<01-10-2010 05:20:29> Installing the SMSMP
<01-10-2010 05:20:29> Passed OS version check.
<01-10-2010 05:20:29> IIS Service is installed.
<01-10-2010 05:20:29> checking WebDAV configuraitons
<01-10-2010 05:20:30>  WebDAV settings is not setup appropriately
<01-10-2010 05:20:30>  [Allow property queries with infinite depth] should be true (false)
<01-10-2010 05:20:30>  [Allow Custom Properties] should be false (true)
<01-10-2010 05:20:30>  [Allow anonymous property queries] should be true (false)
<01-10-2010 05:20:30>  Allow [All users read access to All content] authoring rule should exist (exist)

 

I fixed the problem. The settings were setup OK but for some reason they were not been recognized by the WebDAV component. What I did was open and edit the C:\Windows\System32\inetsrv\config\schema\WEBDAV_schema.xml file. The following parameters were changed:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<element name="properties">
      <attribute name="allowAnonymousPropfind" type="bool" defaultValue="true" />
      <attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="true" />
      <attribute name="allowCustomProperties" type="bool" defaultValue="false" />
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

After that, I restarted the service SMS_SITE_COMPONENT_MANAGER and the log shows: "SMS Site Component Manager successfully installed this component on this site system.". I will wait to see if all components change to OK status.
-------------------
Thanks,

Mike Ditka  - "If God had wanted man to play soccer, he wouldn't have given us arms."

Windows 2008 Core Server Commands in MY LAB I Used

============================================================================================================================================

****************To rename the server Name

Default installations of Windows Server 2008 give the server a name like WIN-94CX1930EF21 or some other obscure pattern that doesn't fit into most computer infrastructures. You can change the computer name using the netdom command. Netdom (which isn't a new tool) is an easy way to change the computer name after Windows Server 2008 is installed on Core Editions. You can also use it on the full installation versions.

It's pretty straightforward to use the netdom command. For example, let's go from the default name WIN-94CX1930EF21 to a computer name of SERVER13. This is the command you would enter:

netdom renamecomputer WIN-94CX1930EF21 /Newname SERVER13

============================================================================================================================================

****************To Add the IP address

In Windows Server 2008 Core installation, the only way to setup IP Address eithe Static or DHCP is from the command line. The following procedure helps setting the IP Address from the command Line using "netsh". This procedure works in Windows Server 2008 (No core installation as well), Windows Server 2003, Windows XP, Windows Vista.

To setup Static IP Address:

From the command prompt:

1. Type

C:\Users\Administrator> netsh interface ipv4 show interfaces

Idx Met MTU State Name

- – — —- ——-

1 50 4294967295 connected Loopback Pseudo-Interface 1

10 20 1500 connected Local Area Connection

This should show the Network Connections. We are looking for the name here. On mine, I have one LAN interface and is named as "Local Area Connection"

2. To set a static IP Address type the following command

C:\Users\Administrator>netsh interface ipv4 set address name="Local Area Connect

ion" source=static address=192.168.0.5 mask=255.255.255.0 gateway=192.168.0.1

The syntax is

netsh interface ipv4 set address name="<ID>" source=static address=<StaticIP> mask=<SubnetMask> gateway=<DefaultGateway>

Where:

ID is the name of the LAN Connection

StaticIP is the static IP address that you are setting

SubnetMask is the subnet mask for the IP address

DefaultGateway is the default gateway

===========================================================================================================================================

****************TO set the DNS Servers :---

set the DNS Servers one at a time with the followind command. For each DNS server, increase the index number.

C:\Users\Administrator>netsh interface ipv4 add dnsserver name="Local Area Connection" address=192.168.0.1 index=1

C:\Users\Administrator>netsh interface ipv4 add dnsserver name="Local Area Conne

ction" address=192.168.0.10 index=2

The syntax is

netsh interface ipv4 add dnsserver name="<ID>" address=<DNSIP>index=1

Where:

ID is the name of the Network Connection

DNSIP is the IP address of your DNS server

This should do. To confirm, do an "ipconfig"

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller

Physical Address. . . . . . . . . : 00-1D-09-D4-2C-8F

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

192.168.0.10

127.0.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled

============================================================================================================================================

****************TO ADD INTO DOMAIN.. cALLED MYDC.COM WITH THE COMPUTER NAME DHCPSRV

netdom join dhcpsrv /domain:mydc /userd:administrator /passwordd:*

or else you can use the below

netdom join dhcpsrv /domain:mydc

　

============================================================================================================================================

-------------------
Thanks,

Mike Ditka  - "If God had wanted man to play soccer, he wouldn't have given us arms."

MSI tools

Here's Sherry Kissinger's review of MSI studio.
 
http://myitforum.com/cs2/blogs/skissinger/archive/2008/09/28/scriptlogic-msi-studio-quick-review.aspx
 
If you're looking for free ones there's a few out there that have hit the ConfigMgr list:
 
http://www.advancedinstaller.com/
 
http://www.appdeploy.com/tools/repackager/
 
http://www.scalable.com/wininstall-le
-------------------
Thanks,

Joan Crawford  - "I, Joan Crawford, I believe in the dollar. Everything I earn, I spend."

WOL:: Wake ON LAN :: Ins and Outs

With Wake On LAN feature, Configuration Manager 2007 activities can be scheduled to take place outside business hours.

1.                 Wake On LAN (WOL) benefits:

·         Achieve a higher success rate for Configuration Manager Activities.

·         Reduces the associated network traffic during business hours.

·         Conserve power by not requiring computers to be left on outside business hours.

 

2.                 Wake On LAN can be used on the following scenarios:

·         Software updates deployment with deadline:

Configuration manager 2007 Send a wake-up transmission prior to the configured deadline for a software update deployment

Wake-up packets are sent only to computers that require the software updates and have not already installed them.

·         Mandatory advertisement for software distribution or task sequence:

Configuration manager 2007 Send a wake-up transmission prior to the configured schedule of a mandatory advertisement, which can be for software distribution or a task sequence.

 

3.                 Walk On LAN overview:

·         Wake-up packet transmissions are sent only from primary site servers only.

·         The default port used by Configuration Manager 2007 to send wake-up packets to target computers is UDP port 9 and can be changed form site settings

·         Secondary site servers or other computers cannot be configured as proxies to send wake-up packets.

·         Wake-up transmissions are not sent to clients when they are on the Internet. Wake On LAN transmissions are always sent at the scheduled time.

·         Wake On LAN independently enabled or disabled for any site in the Configuration Manager 2007 hierarchy

·         Due to advertisements and software update deployments are inherited to child sites, the site server in the child site is responsible for sending the wake-up transmissions to its assigned clients if the site is enabled for Wake On LAN.

·         If Wake On LAN is disabled on a child site, child site will not send the wake-up transmissions to its assigned clients, and client computers in that site will not be sent wake-up packets.

·         ConfigMgr 2007 Client registers the system as busy for the specific wake-up task it receives, this prevents the computer from going back into a sleep state based on its power management settings before the task can complete.

·         Wake On LAN does not return computers to a sleep state and you need to configure power management schemes to shut down or hibernate after a period of inactivity.

·         Computers are woken up before the scheduled activity by 3 minutes before the scheduled activity to ensure that they have completed startup, this setting can be configured with the transmission offset option in a Wake On LAN advanced setting.

·         Mobile devices do not support Wake On LAN capability.

·         Clients running Systems Management Server (SMS) 2003 do not support Wake On LAN.

·         Wake On LAN in ConfigMgr 2007 supports waking up computers in sleep states S1 through S5

4.                 WOL transmission methods

 

·         Unicast transmission

o    Unicast transmission wake-up packet uses the IP address of the target computer from hardware inventory to route to the target computer's subnet, and it uses the Media Access Control (MAC) address of the target computer from hardware inventory to construct the wake-up packet. When the wake-up transmission reaches the target computer's subnet, the wake-up packet is sent directly to the target computer, and If the target computer has changed its IP address since it last sent its inventory information, the wake-up packet will reach the wrong computer but it will not wake it up because the MAC address in the wake-up packet transmission will not match.

o    Switches must forward UDP packets

o    Unicast transmission is secure solution than subnet-directed broadcasts because the packet is sent directly to a computer rather than to all computers on a subnet.

o    Consumes less network bandwidth than subnet-directed broadcast transmissions.

o    Unicast transmission is supported with IPv6.

 

·         Subnet-directed broadcasts

o    Subnet-directed broadcasts transmission wake-up packet uses the Media Access Control (MAC) address and IP subnet address of the target computer from hardware inventory,  The wake-up transmission is sent to the computer's last known subnet, and it is then broadcast to all computers on that subnet, and the computer that has the MAC address specified in the wake-up transmission will respond.

o    Routers must be configured to forward subnet-directed broadcasts.

o    Subnet-directed broadcasts are not supported with IPv6

5.                 Wake On LAN Prerequisites

·         Network cards must support the standard magic packet format.

·         Computers must be configured for wake-up packets on the network card and in the computer BIOS.

·         If subnet-directed broadcast configured, all routers between the site server and target computers must allow IP directed broadcasts, and support IPv4.

·         Hardware inventory must be enabled, and completed an inventory schedule.

·         Client computers must be running the Configuration Manager 2007 client. 

6.                 Sleep States for Wake On LAN

 

·         S0: The computer is on and fully functional.

·         S1: The computer appears to be off with the CPU stopped. RAM is refreshed, and the computer is running in a low power mode.

·         S2: The computer appears to be off with the CPU stopped. RAM is refreshed, and the computer is running in a lower power mode than S1.

·         S3 (Standby): The computer appears to be off with no power to the CPU. RAM is in slow refresh.

·         S4 (Hibernate):  The computer appears to be off with no power to the hardware. System memory has been saved as a temporary file on the hard disk.

·         S5 (Off):  The computer is off with no power to the hardware, and the operating system has been shut down without saving system memory to disk.

-------------------
Thanks,

Stephen Leacock  - "I detest life-insurance agents: they always argue that I shall some day die, which is not so."

Windows 7 64 bit RAM limitations

Here are the upper RAM limits for the different editions of Windows 7:

• Starter: 8GB
• Home Basic: 8GB
• Home Premium: 16GB
• Professional: 192GB
• Enterprise: 192GB
• Ultimate: 192GB

These limits are similar to those for Vista editions, expect that Vista Enterprise and Vista Ultimate have had their upper limits raised from 128GB to 192GB
-------------------
Thanks,

Joan Crawford  - "I, Joan Crawford, I believe in the dollar. Everything I earn, I spend."

windows 2003 slipstreeming

Windows Server 2003 Service Pack 2 Released!

　

Microsoft has just released Windows Server 2003 SP2, currently available for all architectures (x86, x64, & Itanium) in English and German.

New features and bug fixes

Security updates

Download Links:

Windows Server 2003 SP2 for x86

Windows Server 2003 SP2 for x64

Windows Server 2003 SP2 for IA64

Integrating the Service Pack

You can slipstream SP2 into your Windows Server 2003 CD by copying the contents of your CD to a folder on your hard-drive, and issuing the following command:

WindowsServer2003-KB914961-SP2-x86-ENU.exe /integrate:C:\W2k3\

In the example above, this is the x86 installer being used and the Windows Server 2003 CD has been copied to C:\W2k3\

After the process completes, download Microsoft Corporation.img and use it as the bootsector for your CD.

If you're using Nero, it'll look something like this:

Choose CD-ROM (Boot) from the New Compilation's Boot page.

Under Source of boot image data choose "Image file" and Browse to the Microsoft Corporation.img.

Select Enable expert settings (for advanced users only) and set the following: Kind of emulation - No Emulation
Number of loaded sectors - 4
Load segment of sectors - 07C0

-------------------
Thanks,

Mike Ditka  - "If God had wanted man to play soccer, he wouldn't have given us arms."