anyweb

Up until recently, Endpoint Protection came with 4 built-in reports in Configuration Manager 2012. AntiMalware Activity Report Computer Malware Details Top Users By Threats User Threat List As of RC2 there are now six built-in reports AntiMalware Activity Report Computer Malware Details Top Users By Threats User Threat List Infected Computers Dashboard so what are the new reports about ? The fist new Endpoint Protection report shows a nice list of Infected Computers in a timeframe that you can select, you can verify what type of remediation was done via drop down menu and even search by Threat Name (see below). Next we have the Dashboard Report, this report shows lots of nice graphs to give you a graphical view of overall Endpoint Protection status in the collection you selected, malware remediation status, Operation Status of Endpoint Protection clients, Definiton status on Computers (see below) In other words, this report shows summaries of what you can see in the In-console monitoring Endpoint Protection Dashboard in the Monitoring node of the ConfigMgr Console. all in all, very cool stuff, if you havn't yet started experimenting with Endpoint Protection in Configuration Manager 2012 then get started, it's a Blast !

how did you setup SQL and what version of sql did you use

you must install the client otherwise the task sequence will fail.

that's a known issue, just diskpart your hard disc, make sure its got a partition and is formatted and then try again, it'll display correctly

here's your error Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installedwhich probably happened due to the configmgr client failing to install, so examine your ccmsetup.log file to see what it tells you

is it a vmware environment ? perhaps you have a vmware dhcp server causing issues...

well you can't have a tree view or folders, unfortunately

verify DNS, on any of the clients do nslookup. can you ping the fqdn of the Configmgr server ? and vice versa to the clients ? tell me exactly what steps you are taking to deploy the client ?

Summary: The coming Windows 8 beta is looking more and more like it will be called the “consumer preview.” Why the change in nomenclature? Is Microsoft going to position the coming Windows 8 beta as a “consumer preview”? And if so, why? Microsoft officials have repeated recently that the Windows 8 beta release is on track for late February 2012. But one public relations official with the Windows team provided a slightly different message — and one that escaped notice by most of those who read her quote — during the Consumer Electronics Show. As reported by Pocket Lint, Windows Director of Consumer PR, Janelle Poole, stayed on message regarding Microsoft’s continued reluctance to talk about its release-to-manufacturing/ship targets for Windows 8. But, as Windows SuperSite’s Paul Thurrott noted last week, part of Poole’s message deviated from the usual script. Poole called the coming Windows 8 beta “the consumer preview.” Here’s her quote: “We haven’t talked about the release date and we generally don’t. We are talking milestone to milestone, so for us right now we’re talking about the next milestone being the consumer preview happening in late February.” If you know anything about the Windows org, you know words matter. This wasn’t a random throw-away. My first question was whether it’s just the internal Windows consumer PR team calling the beta “the consumer preview” or if the Microsoft brass plan to do the same. I’m hearing that the Windows organization is highly likely to settle on “consumer preview” as the name for the late-February beta. The bigger question — which Thurrott and I discussed during the most recent episode of Windows Weekly — is why Microsoft may label this the consumer preview. Thurrott’s theory was that maybe the developer preview (the September Build version) will be followed by a consumer preview (the beta) and finally the enterprise preview (the release candidate). My theory is more cynical, but not entirely unwarranted. I believe if Microsoft changes the nomenclature, the company is doing so to signify a change that’s been coming for a while now. What used to constitute a “beta” doesn’t really exist in the new Windows world. I said the same during the Windows 7 test period: That the current Windows organization doesn’t show code publicly at all until it’s pretty much set in stone and going to be tweaked very minimally. This makes Windows more predictable, but it also implies that the product is far less likely to incorporate suggested fixes from those outside Microsoft. During the Windows 7 test period, there were still a select group of technical beta testers on whom Microsoft seemingly leaned for real feedback and guidance regarding the product. That team, known internally as the “Test Pilots,” was disbanded after Windows 7 was released. As far as I know, there’s no equivalent to this group this time around. And Senior Program Manager for technical beta testing for Windows, Paul Donnelly, recently left Microsoft to go to Amazon with no replacement named (again, as far as I know). There could be other reasons Microsoft may prefer the “consumer preview” name to “beta.” By claiming a product is far enough along to be used by plain old consumers — and not just techie beta testers — Microsoft officials could be hoping to convince those who think a possible Q3 Windows 8 launch will be too late for Microsoft to shoe-horn its way into the tablet space that Windows 8 is right around the corner. (”Hey, it’s basically done — it’s in consumer preview now!”) Such a name also could help Microsoft’s PC partners who need a way to make new tablets and PCs that they’re bringing to market from now until the time that Windows 8 is shipping seem more up-to-date and palatable. (”This runs the Windows 8 Consumer Preview — so you know it’ll be able to run the final Windows 8 with no problem.”) Microsoft officials aren’t saying anything beyond the fact that the next Windows 8 release is due out in late February and that there is no separate “consumer preview” in the works — meaning, to me, the one-and-only Windows 8 beta is highly likely to be called the “Consumer Preview” when it is released. What’s your take as to why Microsoft is leaning toward calling the beta a “consumer preview” — and what effect (if any) this will have on Redmond, its developers, partners and customers? Thoughts? via > http://www.zdnet.com/blog/microsoft/windows-8-why-the-coming-beta-is-likely-to-be-labeled-the-consumer-preview/11716

is the wds service hanging ? disable the PXE password on it (remove it) on the PXE tab of your distribution point, try restarting/starting the wds service

did you distribute BOTH architecture boot images to your dps ?

post your smsts.log file and we can have a look, as regards what I use, look at the BitLocker and Multifuntion windows-noob.com HTA FrontEnd's, they contain scripts/logic in the task sequence that pretty much does all I need

check Computer Agent settings, Organization Name displayed in Software Center, that's the section where you set it i'm not following your second question, can you re-word it ?

i wouldnt manually copy the files to the folders above at all, instead verify you've distributed both architecture boot images to the distribution points, have you done that yet ? on the DATA SOURCE tab of both architecture boot images, is 'deploy this boot image from PXE..' enabled ?

you can select different task sequences which in themselves can have different boot images attached. to do multiple task sequences see this post (it's configmgr specific but you'll get the idea) using Multiple Task Sequences via PXE, PXE boot to a task sequence menu choice is sometimes a good thing

yes you can change that via custom client agent settings, change the Organization name to whatever you want and deploy those settings to a collection that your computers are in, they will now reflect the new name during os deployment

good info, thanks for sharing, what language and/or regional settings on your server did you have when you were trying to do this initially.

This sounded interesting so thought I’d share. Microsoft has announced (via a post on its Building Windows 8 blog) that Windows 8 will introduce a new file system known as Resilient File System (ReFS) which will include a next generation on-disk storage engine. I should assure you upfront that this will not cause major compatibility issues with NTFS although it is a re-plumbing of the FS not just an upgrade to NTFS. The blog says that it’s “a newly engineered file system…built on the foundations of NTFS, so it maintains crucial compatibility while at the same time it has been “architected and engineered for a new generation of storage technologies and scenarios.” Currently plans are for ReFS to make its first appearance as a storage system in Windows Server 8, after which it will evolve into a system for client storage, then ultimately for boot volumes, which is a tried and true paradigm for rolling out new file systems. If you read the technical blog (by Surendra Verma) referenced in the Sinofsky above post you’ll see that we’re doing this to accomplish some key goals that will serve to future-proof the file system. A synopsis of the key goals are: Maintaining a high degree of compatibility with a subset of NTFS features that are widely adopted. Verifying and auto-correcting data. Optimizing for extreme scale Never having to take the file system offline. Providing a full end-to-end resiliency architecture when used in conjunction with theStorage Spaces feature. (I recommend my technical readers checkout this post on Storage Spaces which will give a more complete view of storage in Windows 8 not just the on-disk engine. For the less technical reader, here’s a quick overview of Storage Spaces, Three Benefits of Windows 8 Storage Spaces) Cheerio chkdsk . ReFS will inherit some of the key features (and code) of NTFS (i.e. ACLs, BitLocker, symbolic links, etc) but, as mentioned above, it’s essentially a re-plumbing from an architectural point of view – specifically, there will be a new on-disk storage engine as the foundation (see graphic below). If you care, the storage engine will exclusively use something called B+ tree structure to represent stored information. I won’t even attempt a description of what that is but suffice to know that this is not a new thing and it leverages page and tables (like a database) for scalability. Verma indicated this will actually mean a simpler system. He also indicated that the file system is being designed to work for a wide range of devices "from the smallest footprint machines to the largest data centers". To give you an idea of the scalability we’re talking here, ReFS will be able to support file names and file paths with as many as 32,000 characters. It can host files as large as 264 bytes (an exabyte = 260), so this is some serious scalability – I’ve included a screenshot of the capacity specs below as well. Oh well, this wasn’t intended to be a technical drilldown but rather just an awareness post to highlight this new technology and remind you that, in fact, we are continuing to advance our infrastructure technology to meet future needs, even on things as mundane as file systems. via > http://blogs.technet.com/b/uspartner_ts2team/archive/2012/01/21/windows-8-to-feature-new-file-system.aspx

right click on a Software Update Group and choose show members, from there, you can select updates and right click to Edit Membership, that will remove the update(s) from the software update groups

check the following:- 1. firewall, disabled it as a test on the client. 2. clientinstall account, verify its a member of the Local Administrators group on the client 3. if the above don't help then verify that the boundary group references tab has the site code checked 4. verify the clientinstall password is correctly specified in client push cheers niall

are you using configmgr rc1 or 2 or ??

glad it's working for you now :-)

hi there, I havn't implemented this, it's a post from Kenny, so you are receieving a mail but it's got the wrong computername, is that your only problem ?

i'd recommend you look into Role Based Access Control to do the console building for you, that way depending on the permissions you choose in the custom role you define, you'll get a different console !

that has no relevance to your issue, your task sequence must be failing in the setup windows and confirmgr step, do you by any chance have that step set to continue on error ? bad idea... please post your entire SMSTS.log file here