Re: [mssms] TS Step to create an Error

Ping -n 1 127.0.0.1. Set your success code to 1. That is what I do to catch errors. Thanks, Chris Brucker On Jul 29, 2014, at 6:05 PM, "Stephen Leuthold" mailto:stephen.leuth...@outlook.com>> wrote: Run command pho.exe /tai /bo /vien Sent from my Windows Phone

Re: [mssms] TS Step to create an Error

lol. Yea, I ran the command "THIS SHOULD CREATE A HUGE ERROR" On Tue, Jul 29, 2014 at 5:04 PM, Stephen Leuthold < stephen.leuth...@outlook.com> wrote: > Run command pho.exe /tai /bo /vien > > Sent from my Windows Phone > -- > From: Todd Hemsell > Sent: ‎7/‎29/‎201

RE: [mssms] TS Step to create an Error

Run command pho.exe /tai /bo /vien Sent from my Windows Phone From: Todd Hemsell Sent: ‎7/‎29/‎2014 4:47 PM To: mssms@lists.myitforum.com Subject: [mssms] TS Step to create an Error What is an easy way to

[mssms] TS Step to create an Error

What is an easy way to make a TS error out?

Re: [mssms] "Region" under Distribution Point

Thanks. On Tue, Jul 29, 2014 at 11:52 AM, Russ Rimmerman < russ.rimmer...@microsoft.com> wrote: > If you set up a cloud DP, it auto-populates with which regional > datacenter you selected to host the Cloud DP instance (West US, East US, > etc). For non-cloud DPs, nothing populates it. > > > >

[mssms] RE: Reference ccmcache folder during deployment

Here's an "old school" reference for ya: SMS Installer v2.0.148 used a built-in variable for the Execute Program action called %INST%\.msi -options This means that no matter what the ccmcache folder/path becomes, it always runs from the location that the .msi file was called from. ;) Dale Nem

RE: [mssms] Deployment warning system?

Matt, I think that is actually how most of these “Ah Shucks” moments happen. Somebody shows the members of the All Systems collection, finds the computer they want and highlight it, but then they click “Add Selected Item” from the task bar… which by default is adding the Collection, not the Res

RE: [mssms] Deployment warning system?

According to the product folks, on average a typical ConfigMgr environment has between 2,000 and 15,000 devices, so let’s take that upper client number for our example. Most organizations that size and smaller have Client Policy set at about 60 minutes. 15,000 Devices / Checking in every 60 Mi

[mssms] RE: Reference ccmcache folder during deployment

Thanks Daniel, I believe it does also as well it requires an .xml file that has to be copied (all done by the installer) I will test out psexec and see if it does work. Kevin From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Tuesda

[mssms] RE: Reference ccmcache folder during deployment

To emulate running as ConfigMgr, use psexec with the -s switch to run as SYSTEM. It sounds like the MSI has something hardcoded inside it that requires the full path, I know with batch you can just use %~dp0 to reference the current directory. msiexec /i "%~dp0application.msi" /q I know it's p

[mssms] Reference ccmcache folder during deployment

I was not sure how to title this and I am not sure if this is possible but I have an MSI file that needs to specifically reference the folder the MSI is located in in order to work. Example: msiexec /i /application.msi SETUPEXEDIR= I am not sure how in SCCM I can make it so when it does copy t

RE: [mssms] "Region" under Distribution Point

If you set up a cloud DP, it auto-populates with which regional datacenter you selected to host the Cloud DP instance (West US, East US, etc). For non-cloud DPs, nothing populates it. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Todd Hemsell Sent: T

RE: [mssms] Deployment warning system?

That’s a good point about someone accidentally adding computers to a collection with a required deployment on it. I’ll have to try and come up with something to detect those changes. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan Sent: Tuesday, Ju

Re: [mssms] Deployment warning system?

I just got the query: Select * From SMS_DeploymentSummary join SMS_Collection on SMS_DeploymentSummary.CollectionID = SMS_Collection.CollectionID where SMS_DeploymentSummary.DeploymentIntent = 2 The query executes quickly and you can pull all the Deployment information as well as the number of us

Re: FW: [mssms] SCCM Distribution Point migration issue

Michael, Thanks! I will give this a shot. Jeff On Tue, Jul 29, 2014 at 11:02 AM, Michael Mott wrote: > Guys, one of our clients had the same issue, I pinged him, hope this > gets thru > > > > *From:* Mitchell, Steven R [mailto:steven.r.mitch...@ehi.com] > *Sent:* Tuesday, July 29, 2014 11:56

Re: [mssms] Deployment warning system?

make a table in mdt db every time a machine starts to image write a row with name and time in mdt select * from that table where date > 30 min ago If it returns more than X rows exit with an error On Tue, Jul 29, 2014 at 11:05 AM, Ryan wrote: > I think it's just as likely someone might add too

[mssms] "Region" under Distribution Point

There is a Region field under distribution points, but no region field on the DP properties. Any idea what populates that column?

Re: [mssms] Deployment warning system?

I think it's just as likely someone might add too many computers to a collection with a required deployment on it. This is why I'd want a little more logic. I'll need to do a little testing to see the most efficient way to get in real time the number of devices something is deployed to. I'm not sur

FW: [mssms] SCCM Distribution Point migration issue

Guys, one of our clients had the same issue, I pinged him, hope this gets thru From: Mitchell, Steven R [mailto:steven.r.mitch...@ehi.com] Sent: Tuesday, July 29, 2014 11:56 AM To: Michael Mott Subject: FW: [mssms] SCCM Distribution Point migration issue Sometimes my emails don’t go through to th

Re: [mssms] Deployment warning system?

no need, you use WMI Eventing on event deployment created check the deployment, do other stuff On Tue, Jul 29, 2014 at 9:55 AM, Ryan wrote: > I was thinking of a scheduled task that runs a script every minute, this > way I can add a tiny bit of logic into it. > > I'd think the over-head would b

RE: [mssms] Deployment warning system?

I was able to get most of this written yesterday afternoon, I’ll work on finishing it up, testing and then getting it to run with the WMI event system (Shout out to Trevor Sullivan’s Power Events module http://powerevents.codeplex.com/) Here is what I’ve written so far, I’ll clean this up with

Re: [mssms] SCCM Distribution Point migration issue

I can't provide any help other than the fact that I see this in an environment I migrated as well. If anyone has insight or suggestions, I would also be grateful! Thanks, Jeff On Tue, Jul 29, 2014 at 10:04 AM, Rick wrote: > We are in the process of moving from SCCM 2007 to SCCM 2012 and have

[mssms] SCCM Distribution Point migration issue

We are in the process of moving from SCCM 2007 to SCCM 2012 and have started Distribution Point migrations. SCCM 2012 reported "completed reassign distribution point" and there were entries in the smsdpprov.log showing that the packages were migrated. We thought the process had completed success

RE: [mssms] RE: ccmexec at login

Or if that SINV\HINV is not relevant disable it on these devices via Client Settings? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Nash Pherson Sent: 29 July 2014 15:27 To: mssms@lists.myitforum.com Subject: [mssms] RE: ccmexec at login > where i

Re: [mssms] Deployment warning system?

I was thinking of a scheduled task that runs a script every minute, this way I can add a tiny bit of logic into it. I'd think the over-head would be the same. Don't WMI triggers run the query you specify every x seconds and trigger the action if something is returned in the query? How would you ex

[mssms] RE: ccmexec at login

> where it left off if it didn't finish. Since these are frozen, every time they restart they are going to think they are past due for hardware inventory and software inventory (as well as any other scheduled ConfigMgr tasks). You might as well only set inventory to happen only as often as your

RE: [mssms] RE: Troubleshooting extreme network utilisation of site server

In the past I've mostly used NIC teaming for fault tolerance. For what you're trying to accomplish, I think you'd still need Link Aggregation on the switches too. Have you thought about doing a network capture and analyzing where/who the traffic is coming? Mike D- From: danielcork...@logan.q

[mssms] RE: ccmexec at login

More than likely soft inv too, as even rebooting it picks up where it left off if it didn't finish. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Tuesday, July 29, 2014 9:40 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: ccm

[mssms] RE: ccmexec at login

Machines check in to see if there's anything new for them. New deployments, AV definitions if you're using SCEP, all the little maintenance items. Take a look at your logs directory after bootup. There's lots of logs that are updated, meaning your client has been doing lots of little tasks.

[mssms] RE: ccmexec at login

Ccmexec could be doing a lot of different things, will need to dig into the logs to confirm. If you suspect inventory, check out InventoryAgent.log. Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Gary Ossewaarde Sent: Tuesday, July 29,

RE: [mssms] Deployment warning system?

Hasn’t the Shy WMI guy already have these triggers in place or blogged out? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan Sent: Monday, July 28, 2014 11:58 PM To: mssms@lists.myitforum.com Subject: Re: [mssms] Deployment warning system? If you thi

[mssms] ccmexec at login

Does anyone know what ccmexec is doing at (first) login? I'm working with a deep-frozen lab, so each login is a "first" login. We don't use roaming profiles/profile redirection at all, either. I ran a boot trace with the Windows Performance Toolkit and noticed ccmexec doing a decent amount of d

RE: [mssms] OSD + PXE assistance

Great feedback. We had been checking just the OS Provisioning collection and not All Systems. Going to change this to make sure the device is showing up in both. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Dean Cunningham Sent: Monday, July 28,

RE: [mssms] Deployment warning system?

A binary that stays in memory 24/7 could monitor this stuff, disable\modify and generate Event Log entries that OpMgr and even Orchestrator could leverage off of. Will not write this tool as you guys have sounded it out here, but if you want help or want to go the route of a binary that can

RE: [mssms] Deployment warning system?

Orchestrator? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan Sent: Monday, July 28, 2014 11:58 PM To: mssms@lists.myitforum.com Subject: Re: [mssms] Deployment warning system? If you think of something, let me know. Otherwise, I've been thinking o

Re: [mssms] Deployment warning system?

Maik made some WMI events that triggered actions. Just need to edit them for criteria and add a different actions. On Mon, Jul 28, 2014 at 4:31 PM, Atkinson, Matt < matt.atkin...@providence.org> wrote: > Hi All, > > > > We’ve been kicking around the idea of some kind of warning system to > noti