anyweb

Step 2. Adding Advanced options to our Application Select our newly created application, right click it and choose Properties the Winzip Properties screen appears, select the Catalog tab and enter some details about the application Click on the Deployment Types tab, and select our application, click on Edit to view the applications deployment types properties, several options exist such as Content, Programs, Detection Method, User-Experience, Requirements, Return Codes and Dependencies. Click on Requirements then click on Add to add a requirement enter the following details, for category choose Machine, select CPU Speed, set the operator to Greater than or equal to and set a value that will work in your lab, eg: 2000 for 2 Ghz. review the requirements you created. Select the Programs Tab. add /qn to the installation switch to install the program silently and click Ok.

Step 4. Enable Active Directory User Discovery In Discovery Methods, select Active Directory User Discovery and double click on it place a checkmark in Enable Active Directory User Discovery and then click on the yellow starburst icon. the New Active Directory container window appears, click on browse and select the default container listed in the Select New Container window click ok and now you'll see the LDAP path is listed click ok again and if you want, adjust the polling schedule (by default it's every 7 days with a 5 minute delta discovery interval) or just leave it as is. Click Ok to close, and then right click on Active Directory User Discovery and choose Run Now to run the Active Directory User discovery now, answer Yes when prompted. In the Wunderbar, click on Assets and Compliance, select Collection Members, All Users in the navigation pane, as the discovery is probably not done yet it may say no items found. right click on All Users and select Update Collection Membership, when done press F5 to refresh and you should see it populated with Active Directory users Next Steps > Now that we have configured Discovery, we are ready for Additional Configuration in Part 3

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. In Part 4 we configured the client Agents and deployed the vNext Client Now we will learn how to Deploy Applications using vNext. But before doing so we need to understand the differences between ConfigMgr 2007 and vNext. Software Distribution in vNext is very different to what we were used to in ConfigMgr 2007. In SCCM 2007, we would typically make a package, the package would contain one or more programs and we would then create an advertisement which targetted the software to a collection. The user would get the software in a variety of ways, silently (mandatory) or optional (via Run Advertised Programs and/or Add Remove Programs in Control Panel). In vNext, the Package and Program is replaced with Application and Deployment Types (Packages and Programs are still available for backwards compatability in vNext but it's considered basic software distribution and not advanced, and more importantly, not recommended.) What we knew as the Advertisement, is replaced with a state based Deployment via detection method, and now the Run Advertised Programs applet is replaced with Software Center. Ok then, let's see how it all works... we will deploy a simple application (in this case, WinZip 15, download the MSI from here), for this Lab, verify that you have enabled Active Directory User Discovery. Perform the following on the vNext server as SMSadmin Step 1. Create an Application In the Wunderbar, click on Software Library, and then click on Application Management in the navigation pane. Select Applications in the navigation pane (or on the right hand side pane), it will say 'no items found' as we have not added any applications yet. In the navigation pane (or in the action pane on the far right) right click on Application and choose Create Application The Create Application Wizard appears, you will notice that the default setting type is set to Windows Installer (Native), you could choose Microsoft Application Virtualization or Mobile CAB files but in this example we will stay with the default (MSI). Browse to the network path of where your MSI is stored (I created a network share on d:\ called sources, in their I created two more sub-directories called apps and winzip.) Include the MSI filename when you browse. eg: \\vnext\sources\apps\winzip\winzip150.msi click Next and you will be informed about the application import, in our case the import succeeded click Next and the General Information screen appears, we can enter some info about the application itself, by default vNext will have picked some values for us (like the install switches) Enter some details about the application, and click on select to create a new Administrative Category, in this example I created a category called Nice to Have, in the Install for User or System drop down menu, select Install for User. review the summary Note: If you get an error like this "Error: The ConfigMgr Provider reported an error connecting to the ConfigMgr site database service" then verify that you added the vNext computer account (vnext$) to the Administrators Group on the vNext server. Review the Confirmation screen and click Close. Our Winzip application should be listed.

and the solution was ...

in your particular case no, but it will help you to figure out how to do it, obviously you'll need to edit the task sequence to ONLY install SNMP if that's what you want, but apart from that you are good to go

yup, it's pretty much covered in this deploy server 2008 post http://www.windows-noob.com/forums/index.php?/topic/543-how-can-i-deploy-windows-server-2008-using-sccm-2007-sp1/ in the roles and features addition from MDT integration, you'll see SNMP is also listed, just select it, and it'll be installed as part of the task sequence cheers niall

if you want us to help you with your sccm problems then you really need to give us some details of what the actual problem is, we cannot guess what the problem is, please provide detailed information about what is wrong and what you've done

Microsoft has taken the big step of distributing its free anti-virus software via the company’s Windows Update system. Microsoft introduced Security Essentials, its free anti-virus software, in September 2009. Microsoft Security Essentials (MSE) is designed to work on Windows XP, Vista and 7 and protects end users against virus threats and spy ware. MSE is Microsoft’s free anti-virus and anti-spyware product that replaced Microsoft’s paid Windows Live OneCare subscription service which was withdrawn last year. The software giant made a u-turn in licensing recently when it announced Small Businesses can now download and install the product on up to 10 PCs. Previously, businesses were unable to install the software legally due to a End User Licensing Agreement (EULA) restriction. Microsoft began distributing Security Essentials as an “optional” update just over a week ago. Although the step marks what is a logical progression of distribution from Microsoft, it could also tempt antitrust lawyers of rival companies Symantec and McAfee. Ed Bott (ZDNet) notes that lawyers at big security software vendors are likely looking into the change very carefully. Microsoft made the update available last week and explained it in Microsoft KB Article 2267621: Winrumors contacted both Symantec and McAfee for comment on Security Essentials. A Symantec spokesperson refused to comment on Microsoft’s recent change stating “Symantec corporate policy does not allow us to comment on the business activities of other companies”. McAfee has not yet responded. Microsoft is currently readying a new version of Security Essentials. An early beta, released in July this year, shows that the future version will include a new protection engine and inspection system. via > http://www.winrumors.com/microsoft-begins-delivering-security-essentials-via-windows-update/

it's available on MSDN now File Name: en_system_center_configuration_manager_2007_r3_x86_dvd_587807.iso Date Published (UTC): 11/1/2010 1:30:02 PM Last Updated (UTC): 11/2/2010 1:59:28 PM SHA1: 6038C2F4566AF8C0A571D3034AC15A8EC8915A35 ISO/CRC: 98ABD360 Available to Levels: VS Pro with MSDN Premium (Empower); Developer AA; MSDN Universal (Retail); VSTS Team Suite (VL); VSTS Architecture (VL); VS Premium with MSDN (MPN); VSTS Test (VL); VS Pro with MSDN Premium (MPN); MSDN Universal (VL); VSTS Database (VL); VS Pro with MSDN Premium (Retail); VSTS Test (Retail); VSTS Development (Retail); VSTS Architecture (Retail); VSTS Team Suite (Retail); VSTS Database (Retail); BizSpark Admin; BizSpark; VS Ultimate with MSDN (VL); VS Premium with MSDN (VL); VS Premium with MSDN (Retail); VS Ultimate with MSDN (Retail); VS Ultimate with MSDN (MPN); Instructions and Resources This product requires that System Center Configuration Manager 2007 with Service Pack 2 be installed first. This installation requires hotfix KB977384.

or using an MDT integrated task sequence have the steps included to install SNMP in a task sequence advertised to a collection containing those comuters.

change the restart computer step back to the way it was, does it work then ? the task sequence i posted didnt use mdt integration, are you using it ?

see if you missed anything from here http://www.windows-noob.com/forums/index.php?/topic/2537-using-vnext-in-a-lab-part-3-additional-configuration/

sounds like the way we do it, except that we build from the installation source (step 3) and then install FAT apps like office 2010, SAP, SEP etc, before the capture in addition, why (in step 8.) are you only installing mandatory updates ? cheers niall

Step 3. Install the Client In the Wunderbar, select Assets and Compliance and select the All Systems collection. In this lab we will select all our systems (ctrl_a) and choose Install Client from the Actions menu, the Client Push Installation Wizard appears, click next Select the Include Domain controllers option (to Install the client on AD1) and click next review the summary click Next and view the completion results Troubleshooting Tip: You can open Task Manager on one of the computers that you are installing the client on, look for CCMSETUP.EXE starting/running After some minutes the clients will be installed, Check the All Desktops and Servers collection, you should see your computers listed with Client = Yes

so after changing it back all ok ?

check the distribution settings of your advertisement see this post for details of what i'm talking about http://www.windows-noob.com/forums/index.php?/topic/2758-how-can-i-copy-files-from-a-package

Step 2. Configure Client Installation Settings In the Administration node of the Wunderbar click on Site Operations, Sites and select our vNext site V01, select Client Installation Settings in the bottom right. Double Click on Client Push Installation to set its' settings and then click on the Accounts Tab. Click on the yellow starburst to add a new account we will use the following user created in AD in part 1 of this series, ClientInstall (a domain admin user in this lab, the screenshot below is from the Active Directory server) After clicking on the yellow starburst, add your ClientInstall details Click on the Client tab and add FSP=VNEXT to add the Fallback Status Point properties to our client installation settings. Click Apply then ok to exit.

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them. Now we will configure the Client Agents and install the client on our Lab systems. Perform the following on the vNext server as SMSadmin Step 1. Configure Default Settings for the Computer Agent In the vNext console, click on Administration, and then right click on Client Agent Settings choose Modify Default Settings. Scroll down to Computer Agent and select Organization Name, change it to your organisation name While we are there let's add the default software catalog website to trusted sites zone, double click on it and change false to true and let's select the default software catalog web site point, double click on it and change the drop down menu to VNEXT Click Ok when done. At this point you can startup Internet Explorer and browse to your Vnext Software Catalog Web Site Point http://vnext/CMSoftwareCatalog/

easy, if it has a Bulletin ID it's a Security Update, if it doesn't have a Bulletin ID it's not a security Update

brilliant, i'd be very interested in you posting details about how you did the trace so others may benefit

German publication n-TV.de reports that O2 has sold out of HTC HD7’s amid strong demand for Windows Phone 7 handsets. Sales so far are said to be in the 5-digit area, with at least 80,000 handsets rumoured, and the carrier is now waiting for further shipments of the handset. The high demand is not just confined to the HTC HD7 either. Vodafone Germany, who will be carrying the HTC Mozart and the Samsung Omnia 7 reports pre-orders are “exceeding expectations”, and were ordering increased quantities to satisfy customers. Even smaller carrier E-plus in Germany, who is carrying the LG Optimus 7, said the OS is receiving a “very positive response”, and is expecting to increase its stock in mid-November. Total sales in Germany this quarter is expected to be in the six figures, according to industry sources. Is Windows Phone 7 lining up to be an unexpected break-out success? Let us know your thoughts below. via > http://wmpoweruser.com/pent-up-demand-means-windows-phone-7-orders-exceeding-expectations-handsets-sold-out/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+WmPowerUser+%28WM+Power+User%29&utm_content=Twitter

Hotfix: KB2448871 This hotfix addresses a known issue in v.Next Beta 1 (build 7470) which can cause SMSEXEC to crash while handling deployment of certain software updates. This crash will occur if there are more than 1100 references in a bundle / update list (this is the combination of direct and indirect references) targeted to collections. Installation Instructions: 1) Install the hotfix on CAS and primary site servers MSFT internal reference: SMS: 243539 SMSSE:6578 ref:- http://myitforum.com/cs2/blogs/brandonlinton/archive/2010/10/30/configmgr-v-next-beta-1-hotfix-kb2448871.aspx Hotfix: KB131665 Problem: The client agent cannot be published to the software update point for software update client deployment. Issue: When enabling software update based client deployment, Windows Server Update Services does not properly register the Configuration Manager client agent. Workaround: Download the software update from the MS Connect site for Configuration Manager and deploy the update to all software update point site system roles. Software Update-Based Client Installation Fails When you enable software update-based client deployment, the Configuration Manager client does not publish to the software update point. The following error is logged in WCM.log: Workaround: Download the software update from the MS Connect site and install this software update on all software update point site system roles. https://connect.microsoft.com/ConfigurationManagervnext/Downloads/DownloadDetails.aspx?DownloadID=29497

first things first 1. I have avertised a task sequence to all systems don't advertise task sequences to All Systems, that is a big no-no, you might accidently install an os *windows 7 or whatever* on ALL SYSTEMS in your organisation (or lab), i've seen it happen to people so don't do it, advertise to your unknown computers collection and/or your Deploy Windows 7 collection. 2. is it vmware or hyperv or something else ? if vmware did you add any drivers to your boot.wim ? 3. so a screenshot why not 4. why does it say you are still validating ? cheers niall

or here ? http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/

How can I make troubleshooting failed deployments easier using a customised boot image Why do we want to do this ? We've all seen OSD fail for some reason or another, wouldn't it be nice to have a set of tools included in your boot.wim file to help you make the job of troubleshooting easier, yes it would. In this example, we will use some 3rd party shareware to allow us to add new abilities to our boot image using easy to type commands which you (or the Technician) can tell the user to type in on an F8 console. The commands are: assistme - remotely list the IP address and disable the firewall, enable winvnc so that a user can view/control a WinPE session to troubleshoot it maillog - compresses and then mails the SMSTS logs to an email address we specify viewlog - open SMSTS.log with Trace32.exe Ok sounds good, how do we do it ? Get the goodies We will utilise some free/shareware applications to assist us in the process, namely:- * trace32.exe (part of Configuration Manager 2007 toolkit) * UltraVNC download the win32 bins 1.0.8.2 Full * rar.exe use rar 3.93.exe for Windows * blat use version 2.6.2 full Download the apps above and extract them somewhere safe. Create the Extrafiles structure Create a directory on a computer and call it Extrafiles, with a structure of subdirectories as follows: c:\Extrafiles c:\ExtraFiles\Windows c:\ExtraFiles\Windows\System32 c:\ExtraFiles\Windows\System32\mailer c:\ExtraFiles\Windows\System32\vnc Now follow these steps: 1. Copy the extracted ultravnc files to C:\ExtraFiles\Windows\System32\vnc 2. run uvnc_settings.exe in c:\ExtraFiles\Windows\System32\vnc to set your desired password and any additional settings, copy the ultravnc.ini it creates to your ExtraFiles\Windows\System32\Vnc if it's not already there as it stores the password and port settings. 3. Copy the extracted blat files (blat.exe, blat.lib, blat.dll) to C:\ExtraFiles\Windows\System32\mailer 4. copy rar.exe to C:\ExtraFiles\Windows\System32\mailer 5. copy Trace32.exe to C:\ExtraFiles\Windows\System32 download the following scripts assistme.cmd maillog.cmd viewlog.cmd ExtraFiles.zip The vnc.reg file mentioned in assistme.cmd is simply what you see in the code below Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\ORL] [HKEY_CURRENT_USER\Software\ORL\VNCHooks] [HKEY_CURRENT_USER\Software\ORL\VNCHooks\Application_Prefs] [HKEY_CURRENT_USER\Software\ORL\VNCHooks\Application_Prefs\winvnc.exe] "use_GetUpdateRect"=dword:00000000 "use_Timer"=dword:00000000 "use_KeyPress"=dword:00000000 "use_LButtonUp"=dword:00000001 "use_MButtonUp"=dword:00000000 "use_RButtonUp"=dword:00000000 "use_Deferral"=dword:00000000 Make sure to copy the three scripts above to C:\ExtraFiles\Windows\System32 and don't forget to configure the Mail settings and email addresses used in maillog.cmd Ok once done, create your new boot image in Configmgr using the Extrafiles method described here Testing the new functionality Add the new boot image to your task sequence (right click on the task sequence, choose properties, advanced and select your new boot image and then test the new functionality by pressing F8 and typing one of the three new commands eg: viewlog hope this helps ! cheers niall