anyweb

In Technet. In the Administration workspace, right-click on Client Settings in Site Configuration and choose Create Custom Client Device Settings. give the custom device settings a suitable name, we will call them Custom Client Device Settings select the following custom settings from the list (we can add/configure more later) Client Policy Computer Agent Software Updates in the left pane, click on the first selected, Client Policy, this is a LAB so lets be more aggresive than the Default setting of 60 minutes in the client policy polling interval, we will set it to 5 minutes in the LAB. This means that once every 5 minutes the Client will contact it's Management Point for any new policy. It's probably best not to set it this aggressively in production as you could generate a lot of traffic from the clients to your Management Point and that will mean two things, increased network load and increased load on the Management Point server, and we all know that the more you load your servers, the slower they get (usually). Next we will configure the Computer Agent settings from the options in the left pane. The first thing you'll want to configure is the Default Application Catalog Website (which we installed above !), so click on Set Website. in the select application catalog website point drop down menu select your choice Set Add default Application Catalog website to Internet Explorer trusted sites zone to True and fill in the Organization Name you want displayed in Software Center (the modern day equivalent of Run Advertised Programs which we had in Configuration Manager 2007) In the left pane select Software Updates and set the Software updates scan schedule from 7 days to 1 day, this will be because we want to synchronize Endpoint Protection definition updates on a daily basis. We will be configuring Endpoint Protection fully in a later part of this series. Apply your changes by clicking OK. Step 3. Deploy our Custom Client Device Settings. Note: Perform the following on the Primary Site server (P01) as SMSadmin. Creating custom client device settings will not take effect until they are deployed to a collection. Right click on our newly created Custom Client Device settings and click Deploy. Select the All Systems Collection and click OK. By doing this action you are applying the Custom Client Device settings to all devices in the All Systems collection. As this is a LAB we don't have many computers in there but that will grow over time. Tip: Now that you have created and deployed our Custom Client Device Settings you can go ahead and create more Custom Client Device Settings with different options as appropriate and then Deploy them to different collections. In addition you can change the priority of the Custom Client Device Settings so that one takes priority over another (highest priority wins). Step 4. Configure Custom Client User Settings Note: Perform the following on the Primary Site server (P01) as SMSadmin. Now that we have our Custom Client Device settings done, let's turn our attention to creating Custom Client User Settings, there are not so many options in these settings but they are useful none-the-less and they are also user specific. They allow you to define whether users can define their Mobile devices and also allow users to set their own User Device Affinity. In the Administration workspace, right-click on Client Settings in Site Configuration and choose Create Custom Client User Settings . Give the new Custom Client User Settings a suitable name and select User and Device Affinity as per the screenshot below for User and Device Affinity, set the drop down menu to True as per the screenshot below, this allows users to decide for themselves if the computer they are using is their primary device (in the My Devices section within the Application Catalog) Click ok to apply the changes. Step 5. Deploy our Custom Client User Settings. Note: Perform the following on the Primary Site server (P01) as SMSadmin. Right click on our newly created Custom Client User settings for site P01 and click Deploy. As these are custom Client User settings you need to deploy them to a User Collection, as this is a LAB we don't have to be fussy so we will select the All Users collection, in production you'll probably want to have more than one Custom Client User Settings defined with different settings for different User Collections. In the Next part of this series we will add the Software Update Point role and use it to deploy the Configuration Manager Client to our computers and then we will verify that they are receiving the Custom Client Device Settings and Custom Client User Settings we've defined above.

you are probably thinking about Forefront Endpoint Protection in Configuration Manager 2007, that was totally different, the only Endpoint Protection Program is scepinstall.exe which is included in the Configuration Manager 2012 client, so once you enable Endpoint Protection and add client computers to a collection targetted with custom client settings which enable Endpoint Protection, they will install the Endpoint Protection Client, try the above and you'll see what i mean

can you post the full error and step from the smsts.log file pls ?

REDMOND, Wash. — May 31, 2012 — Microsoft Corp. today announced the availability of the Windows 8 Release Preview, the next milestone of the highly anticipated Windows 8 operating system. Available for download today in 14 languages at http://preview.windows.com, the Windows 8 Release Preview delivers a fast and fluid experience, along with a new user interface that responds equally well to touch as it does to keyboard and mouse. Since the February release of Windows 8 Consumer Preview, which was downloaded more than 1 million times in the first 24 hours, Windows 8 has become the most tested Microsoft operating system of all time, and with today’s release, it enters its final phase of development before it releases to manufacturing. “We’re thrilled to be at this milestone with the Windows 8 Release Preview,” said Steven Sinofsky, president of the Windows and Windows Live Division at Microsoft. New Apps Provide an Even Richer Experience Windows 8 Release Preview delivers new apps from Microsoft and partners. Highlights include Bing Travel, News and Sports apps, as well as Gaming and Music Xbox apps that integrate with your Zune pass. The Windows 8 Release Preview also features notable improvements to the Mail, Photos and People apps that initially debuted with the Windows 8 Consumer Preview. In addition, Microsoft has worked closely with its partners to deliver apps from around the world through the Windows Store. Beyond the new apps from Microsoft and partners, customers testing the Windows 8 Release Preview will also experience tens of thousands of refinements across the product, such as increased personalization options for the Start screen, improved multimonitor support, refinements to the way people find and download apps through the Windows Store, and new Family Safety features. The new Internet Explorer 10 redefines browsing, particularly for touch-enabled devices. The Web is as fast and fluid as any app, and with new capabilities in the Windows 8 Release Preview such as “flip ahead,” it is just as intuitive. A touch-friendly and power-optimized Adobe Flash Player is now integrated into Internet Explorer 10, and it is also the first browser to feature Do Not Track “on” by default, giving customers more choice and control over their privacy. The Path to Windows 8 Beginning June 2, 2012, Microsoft will roll out the Windows Upgrade Offer in 131 markets, including the U.S. and Canada. Consumers who buy eligible Windows 7-based PCs through Jan. 31, 2013, can purchase an upgrade to Windows 8 Pro for an estimated retail price of $14.99 (U.S.) during the time of the promotion. More information about the Windows Upgrade Offer will be available June 1. In addition to the Windows Upgrade Offer designed for consumers buying new Windows 7-based PCs, Microsoft will also announce other offers in the coming months that will help consumers with existing Windows 7-based PCs upgrade to Windows 8 when it is generally available. In the next month, Microsoft will further detail the value Windows 8 brings to businesses at TechEd North America. More information about Windows 8 and how to download the Windows 8 Release Preview is available at http://preview.windows.com. Founded in 1975, Microsoft (Nasdaq “MSFT”) is the worldwide leader in software, services and solutions that help people and businesses realize their full potential. Some information relates to a prerelease product, which may be substantially modified before it is commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. Note to editors: For more information, news and perspectives from Microsoft, please visit the Microsoft News Center at http://www.microsoft.com/news. Web links, telephone numbers and titles were correct at time of publication, but may have changed. For additional assistance, journalists and analysts may contact Microsoft’s Rapid Response Team or other appropriate contacts listed at http://www.microsoft.../contactpr.mspx.

what os do you want to Deploy ?

Microsoft appears to be taking steps to remove legacy code from its Windows 8 operating system that will prevent modifications and hacks to re-enable the Start button and Start Menu. Windows watcher Paul Thurrott reports that the company has been "furiously ripping out" legacy code in Windows 8 recently that lets third parties bring back the Start button, Start Menu, and other legacy parts of the desktop interface. Thurrott claims that several well-known UI hacks that enabled the Start Button in the Consumer Preview do not work on the Release Preview. Despite a growing debate over Metro on desktop PCs, Microsoft doesn't appear to be willing to offer a choice of traditional desktop or Metro with its upcoming Windows 8 release, opting to continue to fuse the pair together. Thurrott claims there will not be an option to boot directly into the desktop for business or power users, and that Windows Server 12 will also boot into Metro. Microsoft's approach will anger some who prefer the traditional desktop over the new fullscreen Metro world, but the focus is on convincing developers to build Metro style apps. The Windows 8 Release Preview will debut today, where we're expecting to see some improvements for multi monitor setups and tweaks to some of the core Metro style applications, but Microsoft has already revealed that it plans to drop the Aero UI before RTM so there's clearly room for additional changes before the operating system ships later this year. source > http://www.theverge.com/2012/5/31/3054348/microsoft-windows-8-start-button-legacy-code-removal?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed%3A+WinRumors+%28WinRumors%29

it was released in April, and the interest about this product is clear to see on windows-noob.com, so let everyone know are you using System Center 2012 Configuration Manager yet ?

yesterday Neowin blogged about a post that was made on the MSDN blogs about the release of Windows 8 Release Preview today, May 31st. In anticipation of the availability of those files later today, i'm posting the download links here: Windows 8 Release Preview: Download here Windows 8 Driver Kit: Download here Visual Studio 2012 Professional: Download here cheers niall

it's all explained in the guides, to install the SCEP client you do so via custom client agent settings and custom client antimalware settings, have you configured these ? is the ConfigMgr client installed on your clients yet ? once your systems end up in a collection targetted with the Custom Client settings (for enabling Endpoint Protection) and Custom Antimalware policies, they'll get SCEP installed and configured.

just noticed this now, sorry for missing it, you should take a look at the following post (and recording if you want), the powerpoint contains notes in the slide notes which will help you in choosing how to build and capture and then later deploy,

if you follow the guides you'll see theres an option of deploying the client via Client Push, however that is one of many ways to deploy it.

did you select Definition Updates in Classsifications ? you need the ConfigMgr client installed on the computers before you can implement Endpoint Protection, the machines above say 'client =no' so do they have the client installed, or not

you can set the variables in many ways such as via collection variables computer variables HTA sets the variables steps in the task sequence a script glad to hear you got it working

you can simply disable both steps in your task sequence and do a test run, maybe you'll find out before me

if you followed part 5 then why are you running a separate SCEP 2012 install ? when you configured the Software Update Point did you check your wsyncmgr.log as explained in part 2 as described here

please raise one thread per topic, your orginal question was about installing ConfigMgr, now it is installed. Raise a new topic about your Endpoint Protection problem, it keeps things clearer and easier to follow/troubleshoot...

are you setting the SMSTSUdaUsers variable like i do in my example ? http://www.windows-noob.com/forums/index.php?/topic/4522-using-sccm-2012-rc-in-a-lab-part-10-using-prestart-and-extrafiles-to-get-more-out-of-uda/

yes, go to the download page again, here it is. and download this version, click on Show hotfixes for all platforms and languages (3) to see every download... SQL Server 2008 R2 All (Global) x64 SQLServer2008R2_SP1_CU6_2679367_10_50_2811_x64

you are using SQL Server 2008 R2 RTM, ie you are missing the service pack and needed Cumulative Updates. See here for a list of supported versions of SQL Server. Step 10 of using System Center 2012 Configuration Manager - Part 1. Installation - CAS here shows you what to download and install.

that can't be right, can you post the correct error message please ? and the number is the package id of the package in question, add it to your dp and you'll be ok

thanks for posting the resolution ! and good luck with the rest of it

no, SQL Server 2012 is not yet supported so don't use it until it is. The supported versions of SQL Server are listed in my Configuration Manager 2012 RTM guide here.

Configuration Manager client computers can be domain members, or workgroup members however if they are workgroup members you'll need to manage them differently, for example you can't install the client using client push to workgroup computers.

where are you seeing that error ? in the logs or in the setup installation console, can you post the ConfigMgrSetup.log file here please ? did you add the installation account (SMSadmin) as a sysadmin on your sql server as described below ?

is your wds server on the same lan/vlan as the client ?