Skip to main content


Showing posts from February, 2009

writing event log entries with powershell

just some more stuff i picked up hanging out with the #powershell guys.   # Writing an event $EventLog = New-Object System.Diagnostics.EventLog( 'Application' ) $EventLog.MachineName = "." $EventLog.Source = "WorkstationEngineering" $EventLog.WriteEntry( "Testing Event" , "Warning" , $EventID)   # viewing overloads ($myevent.WriteEntry).OverloadDefinitions   # Listing enums [enum]::getvalues([system.diagnostics.eventlogentrytype])

trickling members from one collection to another collection in configmgr

UPDATE: one of my coworkers was using this script to push out a hefty backup agent.  he couldn’t get it to run so while looking at it, i realized the last if/then condition was flawed.  it was looking for members of a compared object when no comparison was issued.  if the second collection is empty and the first collection is greater than the number of clients to send at once, it would fail.  anyway, all fixed. 1000 clients. 1 gb payload. generally not the situation you want to be in when you’re deploying something over configmgr.  it’s not that it can’t handle it.  there are just certain provisions you have to take so that you do not overwhelm your distribution point(s).  one way to get through this to break down your collection into multiple collections and tie advertisements to them. an easier way to manage this would be to percolate members from one collection into another.  if you’ve been around awhile, you may remember the script that rick jones wrote to do just this.  yo