The MVPS HOSTS file was recently updated [May-23-2012]
http://winhelp2002.mvps.org/hosts.htm

Download: hosts.zip (145 kb)
http://winhelp2002.mvps.org/hosts.zip

How To: Download and Extract the HOSTS file
http://winhelp2002.mvps.org/hosts2.htm

HOSTS File - Frequently Asked Questions
http://winhelp2002.mvps.org/hostsfaq.htm

Note: the "text" version makes a great resource for determining possible unwanted connections ...
http://winhelp2002.mvps.org/hosts.txt (590 kb)

Get notified when the MVPS HOSTS file is updated
http://winhelp2002.mvps.org/updates.htm

 If you find the MVPS HOSTS file useful ... please consider a donation ...

Posted by winhelp2002 | with no comments
• 15206 total items in database
• 29 new IE CLSID's
• No new IE Restricted site zone entries
• No new entries for Mozilla

29 Internet Explorer
0 Restricted Sites
0 Firefox

15206 items in database

http://www.javacoolsoftware.com/downloads.html

Posted by Don
Filed under:

I found a class new to me - Msft_Providers and this got me interested in WMI providers.

PS> Get-CimInstance -Class Msft_Providers | select -ExpandProperty provider
Msft_ProviderSubSystem
SCM Event Provider
WmiPerfClass

 

That seems a bit low. Digging a bit more I got back to the old favourite __provider.

Get-CimInstance -Class __provider | Measure-Object

produces an answer of 43 – not quite the answer to life, the universe and everything but close.

Is there any overlap between the two groups of providers?

$providers = Get-CimInstance -Class Msft_Providers | select -ExpandProperty provider           
Get-CimInstance -Class __provider | where Name -in $providers | select Name

 

provides the answer

Msft_ProviderSubSystem  

SCM Event Provider

 

In case you were wondering – “Starting with Windows Vista, the WMIPerfClass Provider and the WMIPerfInst Provider dynamically provide performance counter data for the WMI Performance Counter Classes.”

see http://msdn.microsoft.com/en-us/library/windows/desktop/aa392740(v=vs.85).aspx

 

One interesting property is the Hosting Model

Get-CimInstance -Class __provider | select HostingModel -Unique

Decoupled:NonCOM
NetworkServiceHost
WmiCore
LocalSystemHost
LocalServiceHost

NetworkServiceHost:[ReliabilityMetricsProvider]

 

But what do these mean

Full explanations for these and the other hosting models can be found at

http://msdn.microsoft.com/en-us/library/aa392509(VS.85).aspx

WmiCore - Activate provider in host to the WMI service. This hosting model is only supported for operating system components.

WmiCoreOrSelfHost - Activate provider in host to the WMI service or as local server. This hosting model is only supported for operating system components.

SelfHost - Activate provider as a local server implementation.

Decoupled:Com - Activate provider as a decoupled COM provider. See http://msdn.microsoft.com/en-us/library/aa390882(v=vs.85).aspx
 
Decoupled:NonCom - Activate provider as a non-COM event provider.
 
LocalSystemHost - Activate provider in the provider host process that is running under the LocalSystem account.

LocalSystemHostOrSelfHost - The provider is self-hosted or loaded into the Wmiprvse.exe process running under the LocalSystem account.

NetworkServiceHost - Activate provider in the provider host process that is running under the NetworkService account.

LocalServiceHost - Activate provider in the provider host process that is running under the LocalService account.

NetworkServiceHostOrSelfHost - The provider is self-hosted or loaded into the WmiPrvse.exe process running under the NetworkService account. NetworkServiceHostOrSelfHost is the default configuration when the HostingModel property in __Win32Provider is NULL. Because NetworkServiceHostOrSelfHost is the default, providers from earlier operating systems can continue to work in Windows Vista, Windows Server 2008, and later operating systems.

Get-CIMInstance is a new cmdlet in PowerShell v3. It is part of the new API for working with WMI. I will be blogging about these in greater detail over the next weeks and months as Powershell v3 is released.

More information on providers and the CIM cmdlets can be found in PowerShell and WMIwww.manning.com/powershellandwmi

Pessoal, no domingo passado eu respondi os mais de 300 e-mails que eu estava em dívida com a comunidade. Porém durante um evento em SP algumas pessoas da comunidade me cobraram a resposta de e-mails que eu não havia recebido. Analisando este caso percebi que desde 12/2011 o meu HOST estava simplesmente SUMINDO com alguns e-mails que vinham do meu BLOG ou direto pro meu endereço CONTATO@CLEBERMARQUES.COM e com isso eu deixei de atender muita gente, com certeza.

 

Felizmente já resolvi a situação: TROQUEI DE HOST. Espero que entendam a situação, e se você me encaminhou algum e-mail nos últimos 6 meses e não recebeu resposta, me desculpe, mas estou aqui para receber seu contato e te ajudar!

 

Obrigado pela leitura e até a próxima publicação,

Abraço.

 

Cleber Marques

Microsoft MVP - System Center Cloud and Datacenter Management
CleberMarques.com | Meu Blog | MOF.com.br | CanalSystemCenter.com.br

Posted by Cleber Marques | with no comments
Filed under: ,

Smartphone users should always be careful of applications installed and links selected as malware attacks continue to increase for this vector

Android Malware - McAfee shows increase for Q1 2012
http://securitywatch.pcmag.com/none/298206-android-malware-spikes-in-2012

QUOTE: According to McAfee the number of malicious Android apps surged from the hundreds to the thousands in the first quarter of 2012, compared to the same period last year. In "McAfee Threats Report: First Quarter 2012" the company reported that the number of mobile threats on Android reached 7,000 samples, while Symbian, Java ME (mobile edition), and "others" combined reached only 1,000.

The figures are alarming, but it's still fairly easy to keep your Android devices clean of malware. For starters, steer clear of third-party app stores (outside Google Play or Amazon App Store for Android). Unlike in the PC environment where worms can spread without any user involvement, mobile infections still rely on users installing malicious apps.

Posted by Harry Waldron | with no comments

Windows Multi Control System is a rogue anti-spyware program from the Rogue.FakeVimes family. This program is classified as a rogue as it displays false information in order to trick you into purchasing the program. This particular variant is spread via two methods. The first method is the use of hacked web sites that exploit visitor's vulnerable programs in order to install the rogue without their permission. The second method uses web sites that display fake online anti-malware scanners that pretend to scan your computer, state that it is infected, and then prompt you to download and install Windows Multi Control System in order to clean it.

Once the rogue is installed on your computer it will be configured to start automatically when Windows starts. Once started it will perform a fake scan and then state that there are numerous infections present. If you attempt to use the program to remove these infections, though, it will state that you first need to purchase it before it can do so. This is a scam as the scan results are all fake, and in many cases, the infected files do not even exist on your computer. Therefore, please ignore the scan results and do not purchase the program.

http://www.bleepingcomputer.com/virus-removal/remove-windows-multi-control-system

Posted by Don

2012-05-23
Trojans

+ Bancos + Bancos.Santander ++ BoanKeeper ++ Win32.Banker.prx ++ Win32.Barys.bho + Win32.Muollo + Win32.OnLineGames.down + Win32.OnLineGames.gen ++ Win32.Typic.bga + Win32.ZBot
Total: 2541906 fingerprints in 792410 rules for 6658 products.

http://www.safer-networking.org/en/index.html

Posted by Don
Filed under:

Holal Qué tal.

Continuando con el ejemplo del post anterior (http://bit.ly/oh0m9k), referente al manejo de imágenes en WPF, ejemplificaremos el manejo de las imágenes de la misma manera pero, esta vez, utilizando enlace a datos y la clase Binding.

Antes, tenemos que hablar un poco de lo que es el enlace a datos con WPF. Trataré de ser breve y de no ahondar tanto para llegar más rápido a lo que nos ocupa.

El enlace a datos en objetos de la interfaz de usuario de WPF está determinado a través de la clase Binding, expuesta en la mayoría de las ocasiones, dentro del código de XAML definiendolo directamente en la asignación del valor de la propiedad que se quiere enlazar.

Debemos tener en cuenta que para realizar el enlace de datos, se debe contar con las condiciones necesarias para que esto sea posible, empezando por identificar las propiedades que podemos enlazar, las cuales deben ser propiedades de dependencia y que no sean de solo lectura. Otra consideración importante, es que las propiedades se enlazan a valores establecidos en objetos con la finalidad de mostrar los datos que contienen sus propiedades, en la interfaz de usuario.

Comúnmente se asignan los valores de los objetos directamente a las propiedades de los controles contenidos en la interfaz de usuario desde el código, teniendo complicaciones al momento de implementar la actualización de la información presentada en la interfaz de usuario de manera dinámica cuando los valores en las propiedades de nuestros objetos cambian durante la ejecución del código, derivando en la definición de más código que incluyen condiciones en la ejecución y eventos que pudieran estar de más con el uso del enlace a datos utilizando Binding.

La clase Binding ofrece mecanismos prácticos para que la información que se muestra al usuario sea la misma que contienen las propiedades de nuestros objetos.

Para iniciarnos en el uso de Binding debemos tener presente que, para que la información que contienen las propiedades de nuestros objetos se muestren correctamente en la interfaz de usuario utilizando enlace a datos en WPF y XAML, deben existir cuatro elementos necesarios para que funcione de la mejor manera. Primeramente debemos definir el Destino del enlace, el cual será un control de la interfaz de usuario, dicho de una mejor manera, un objeto de dependencia. Seguido de esto, identificaremos en el objeto de dependencia, la propiedad de dependencia que será la encargada de mostrar el dato. Con esto tenemos definido ya el destino, ahora bien, debemos identificar el objeto de origen, el cual expondrá  los datos y por último, la propiedad en este objeto que será la que proveerá el dato a la interfaz de usuario.

Con esto, hemos definido los cuatro elementos necesarios para realizar el enlace a datos utilizando Binding en WPF. En resumen, los cuatro elementos son un objeto de destino del enlace, una propiedad de destino del enlace, un objeto de origen del enlace y una propiedad de origen del enlace. Recordemos que la propiedad de destino de enlace debe ser una propiedad de dependencia.

Como podrán observar, la propiedad de origen de destino no es necesariamente una propiedad de dependencia y los objetos de origen de enlace no están restringidos a ser únicamente los personalizados, también, los propios elementos de la interfaz de usuario pueden ser objetos de origen de enlace. Como veremos en otra publicación en otra ocasión.

Para ejemplificar, dentro de nuestro ejemplo tenemos declarado un control Image denominado imgFoto, este control mostrará una imagen como dato enlazado. La declaración XAML será algo como esto:

<Image x:Name="imgFoto" Width="100" Height="100" Margin="5"

        Source="{Binding Path=Image}" />

 

Podemos notar ciertas características en la definición del enlace a datos, primeramente veremos que la propiedad Source se declara como habitualmente se hace, sin embargo, dentro de la acotación definida por las comillas se agrega la declaración del enlace entre llaves ({}),  se pone la palabra Binding que hace referencia a la clase del mismo nombre y en seguida la asignación de Path con el nombre de la propiedad de origen del enlace, misma que está definida en el objeto de origen del enlace.

La clase Binding expone una propiedad denominada Path, esta propiedad es la que establece el enalce con la propiedad de origen. Es una propiedad predeterminada, a menos que se requiera la declaración explicita se podrá omitir, y lo que se escriba inmediatamente enseguida de Binding será tomado como el nombre de la propiedad de origen del enlace y será asignado a la propiedad Path. Teniendo en cuenta esto, la declaración puede quedar como sigue:

<Image x:Name="imgFoto" Width="100" Height="100" Margin="5"

        Source="{Binding Image}" />

 

De este modo el código de nuestra ventana quedará conformado de manera inicial como lo siguiente:

<Window x:Class="EjemplosWPF.MainWindow"

        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

        Title="MainWindow" Height="350" Width="525">

    <Grid>

        <StackPanel HorizontalAlignment="Center" VerticalAlignment="Center">

            <Image x:Name="imgFoto" Width="100" Height="100" Margin="5"

                    Source="{Binding Image}" />

            <Button x:Name="btnFoto" Width="100" Height="25"

                    Content="Agregar Foto" Margin="5" Click="btnFoto_Click"/>

        </StackPanel>

    </Grid>

</Window>

 

Debemos declarar ahora la clase que define al objeto de origen del enlace, será una clase simple y estará definida como sigue:

public class Foto

{

    BitmapImage image;

    public Foto()

    {

        image = null;

    }

 

    public BitmapImage Image

    {

        get

        {

            return image;

 

        }

        set

        {

            image = value;

       }

 

    }

}

 

Para efectos del ejemplo, esta clase la pueden crear enseguida de la clase de la ventana, dentro del mismo Namespace.

En la ventana, el código quedaría de la siguiente manera:

public partial class MainWindow : Window

{

    Foto foto;

    public MainWindow()

    {

        InitializeComponent();

        foto = new Foto();

        DataContext = foto;

    }

 

    private void btnFoto_Click(object sender, RoutedEventArgs e)

    {           

        if (foto.Image == null)

        {

            OpenFileDialog openFile = new OpenFileDialog();

            BitmapImage b = new BitmapImage();

            openFile.Title = "Seleccione la Imagen a Mostrar";

            openFile.Filter = "Todos(*.*)|*.*|Imagenes|*.jpg;*.gif;*.png;*.bmp";

            if (openFile.ShowDialog() == true)

            {

                if (new FileInfo(openFile.FileName).Length > 131072)

                {

                    MessageBox.Show(

                        "El tamaño máximo permitido de la imagen es de 128 KB",

                        "Mensaje de Sistema",

                    MessageBoxButton.OK,

                    MessageBoxImage.Warning,

                    MessageBoxResult.OK);

                    return;

                }

 

                b.BeginInit();

                b.UriSource = new Uri(openFile.FileName);

                b.EndInit();

                imgFoto.Stretch = Stretch.Fill;

                foto.Image = b;

 

                btnFoto.Content = "Quitar Foto";

            }

        }

        else

        {

            foto.Image = null;

            btnFoto.Content = "Agregar Foto";

        }

           

    }

}

 

Como podemos observar, no es muy diferente al código del ejemplo anterior, sin embargo podemos recalcar algunos cambios sustanciales.

Primero, se ha incluido la declaración de la variable foto, que es del tipo Foto, mismo que está definido por la clase que se muestra más arriba.

Segundo, en el constructor de la clase de la ventana, se agregó la instancia de la variable foto y se asigna la propiedad DataContext de la misma ventana. Aquí quiero hacer un paréntesis y hacer una observación sobre DataContext. Al asignar el objeto foto como DataContext del formulario, hará que en todas las declaraciones de Binding se asuma que los valores de Path son propiedades de origen de enlace contenidas en el objeto foto. Si existieran más controles con la definición de Binding, además del control imgFoto, los valores asignados a las propiedades Path de estos, estarían en el entendido de ser propiedades de origen de enlace definidas en el objeto foto. Si por el contrario, se asignara directamente a la propiedad DataContext del control imgFoto, solo se aplicarían los enlaces de datos a este control en exclusivo. Veremos un ejemplo de esto en la siguiente publicación.

Tercero; las validaciones cambiaron, de validar la propiedad Source del control imgFoto a validar la propiedad Image del objeto foto.

Cuarto; ahora en vez de asignar la propiedad Source del control imgFoto, se asigna la propiedad Image del objeto foto, que será la propiedad de origen del enlace, como podemos ver en el código XAML, la propiedad Source del control imgFoto está asignada con un Binding cuya propiedad Path, es la propiedad Image del objeto foto, de esta manera por ser del mismo tipo de valor que recibe la propiedad Source, se debe mostrar al momento en el control imgFoto.

Quinto; ahora se anula la propiedad Image del objeto foto en lugar de anular la propiedad Source del control imgFoto, que tendrá el mismo comportamiento que en el punto cuarto, quitando la imagen del control imgFoto.

Pues bien, aclarando esto, construimos el proyecto y ejecutamos… y… después de ver que al agregar la foto, no se muestra… nos desesperamos y caemos en la cuenta de que el Binding no sirve para nada… No, no es ninguna falla. El Binding para que sea dinámico debe estar notificado por un desencadenador (trigger), que actualizará la interfaz de usuario al momento en que cambia la propiedad. Para lograr esto debemos modificar un poco el código, solo en la clase Foto y en el XAML de la ventana, el código de la ventana se queda como está.

En la declaración de XAML, tenemos lo siguiente:

<Image x:Name="imgFoto" Width="100" Height="100" Margin="5"

        Source="{Binding Image}" />

 

Debemos modificar esta declaración incluyendo la propiedad UpdateSourceTrigger asignándola con el valor PropertyChanged. Quedando como sigue:

<Image x:Name="imgFoto" Width="100" Height="100" Margin="5"

        Source="{Binding Image, UpdateSourceTrigger=PropertyChanged}" />

 

Podemos observar que la propiedad se define explícitamente a diferencia de la propiedad Path, que ya habíamos comentado, y también vemos que las propiedades de Binding se incluyen en la declaración separadas por comas. Pero aun así, no es suficiente, ya que el valor PropertyChanged hace alusión a un evento que se desencadena en el objeto de origen del enlace, y debe incluirse en este como una implementación de la interfaz INotifyPropertyChanged que es parte del namespace System.ComponentModel. Así que haremos las modificaciones correspondientes. Primeramente al inicio de nuestro archivo de clase incluimos la declaración:

using System.ComponentModel;

 

Una vez incluida esta declaración, modificaremos la clase Foto para que quede de la siguiente manera:

public class Foto : INotifyPropertyChanged

{

    BitmapImage image;

    public Foto()

    {

        image = null;

    }

 

    public BitmapImage Image

    {

        get

        {

            return image;

 

        }

        set

        {

            image = value;

            PropertyChanged(this,

                new PropertyChangedEventArgs("Image"));

        }

 

    }

 

    public event PropertyChangedEventHandler PropertyChanged;

}

 

Podemos observar que incluimos en la declaración de la clase las adecuaciones para implementar la interfaz INotifyPropertyChanged, además, se declara el evento PropertyChanged que de manera implícita implementa el miembro PropertyChanged de la interfaz INotifyPropertyChanged. Ahora bien, en la propiedad Image de la clase, en el descriptor de acceso set se lanza el evento PropertyChanged, como parte de los argumentos del evento se incluye como parámetro el nombre de la propiedad como un string. Así, toda vez que se asigne un valor a la propiedad Image del objeto foto,  se lanzará el evento PropertyChanged e informará del cambio del valor de la propiedad a Binding para que el contenido de las propiedades enlazadas se actualicen.

Ahora sí, hechas las modificaciones pertinentes, ejecutemos el código para ver complacientes que todo funciona como se esperaba que lo hiciera.

Este ejemplo es un adelante a lo que sigue, que es cómo manejar las imágenes como datos que pueden salvarse como parte de un registro en una base de datos. El próximo articulo estará dirigido a esto en el que incluiré todo lo necesario para manejar la imagen con bases de datos.

Espero que este artículo sea de utilidad y nos vemos en la próxima.

Octavio Telis.

 

Posted by Octavio Telis Aynés | with no comments
Filed under: , , ,

If you are still seeing these updates get offered up over and over again...

and you are running Windows XP or Server 2003 sp2

...and you have "download but do not install" as your windows update settings

Try this - you'll need to reset your Windowsupdate settings.

http://support.microsoft.com/kb/971058 Use that fixit to reset it.

The underlying issue was a Microsoft update detection problem with http://support.microsoft.com/default.aspx?scid=kb;en-us;2656353.  This update supercedes (takes the place of) KB2518864, KB2633880 and KB2572073.  When KB2656353 was removed from the update servers to get ready for a rerelease, it caused an issue where these three old .net's got reoffered. 

For those with automatic updates enabled, you got .net's over and over again but could go to the yellow icon, click on it, and get rid of the faulty detection.  For anyone with "download but do not install", you have the patches stuck in your software distribution folder.

So here's what I'm recommending, use the fixit in http://support.microsoft.com/kb/971058 to reset your software distribution folder.

Let me know if that works.

That didn't work.  Try this:

Method 10: Empty the software distribution folder

  1. Click Start, click Run, type services.msc, and then click OK.

    Note On a Windows Vista-based computer, click Start, type services.msc in the Start Search box, right-click services.msc, and then click Run as administrator.
  2. In the Services (Local) pane, right-click Automatic Updates, and then click Stop.
  3. Minimize the Services (local) window.
  4. Select all the contents of the Windows distribution folder, and then delete them.

    Note By default, the Windows distribution folder is located in the drive:\Windows\SoftwareDistribution folder. In this location, drive is a placeholder for the drive where Windows is installed.
  5. Make sure that the Windows distribution folder is empty, and then maximize the Services (local) window.
  6. In the Services (Local) pane, right-click Automatic Updates, and then click Start.
  7. Restart the computer, and then run Windows Update again.
Posted by bradley | 4 comment(s)
Filed under:

So I had a server at home with these three updates still being offered.  I clicked on the yellow icon to attempt to install them.  I got this window, I clicked close and the yellow icon went away and I'm no longer being offered these updates.

If you see differently holler, as I can't repro anymore getting these updates.

Posted by bradley | 2 comment(s)
Filed under:

Where-Object – aliased to where, but never, ever, ever, ever to ? – had a very simple syntax in PowerShell v2

Where-Object [-FilterScript] <scriptblock> [-InputObject <psobject>] [<CommonParameters>]

It was normally used as

Get-Process | where {$_.CPU -gt 25}

The –FilterScript parameter (positional as 1 so don’t have to use it) supplies a script block that performs the filtering. In this case it looks at the current object on the pipeline (indicated by $_) and compares the CPU property to 25. If the property has a greater value it is passed.

Any of the comparison operators could be used in the filter block.

With PowerShell v3 it gets easier

Get-Process | where CPU -gt 25

We can just give the property name, the comparison operator and the value. 

This only works for a single property. You can’t do this

PS> Get-Process | where CPU -gt 25 -and Handles -gt 2000
Where-Object : Cannot bind parameter because parameter 'gt' is specified more than once. To provide multiple values to
parameters that can accept multiple values, use the array syntax. For example, "-parameter value1,value2,value3".
At line:1 char:45
+ Get-Process | where CPU -gt 25 -and Handles -gt 2000
+                                             ~~~
    + CategoryInfo          : InvalidArgument: (:) [Where-Object], ParameterBindingException
    + FullyQualifiedErrorId : ParameterAlreadyBound,Microsoft.PowerShell.Commands.WhereObjectCommand

You have to go back to

Get-Process | where {$_.CPU -gt 25 -and $_.Handles -gt 2000}

but hang on a minute the error message said that gt is a parameter!

If you look at the help file for where-object you will see lots of lines like this

Where-Object [-FilterScript] <ScriptBlock> [-InputObject <PSObject>] [<CommonParameters>]
  
Where-Object [-Property] <String> [[-Value] <Object>] [-EQ [<SwitchParameter>]] [-InputObject <PSObject>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -Contains [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -GE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -In [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CContains [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CEQ [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CGE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CGT [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CIn [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CLE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CLike [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CLT [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CMatch [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CNE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CNotContains [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CNotIn [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CNotLike [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -CNotMatch [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -Is [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -IsNot [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -LE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -Like [<SwitchParameter>] <CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -LT [<SwitchParameter>] <CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -Match [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -NE [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -NotContains [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -NotIn [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -NotLike [<SwitchParameter>] [<CommonParameters>]
   
Where-Object [-Property] <String> [[-Value] <Object>] [-InputObject <PSObject>] -NotMatch [<SwitchParameter>] [<CommonParameters>]

The first option is the PowerShell v2 version. 

Notice that the comparison operators are switch parameters and each is in a different parameter set – thats why you can’t have multiples

This is a very useful addition to where-object that simplifies syntax (we often only perform a single comparison in the filter) and reduces typing.

It still doesn’t change the fact that you should never, ever, ever, ever alias where-object to ?

Posted by RichardSiddaway | with no comments
Filed under:

Sua empresa usa o System Center Service Manager (SCSM)? Se sim, gostaria de fazer parte de uma rápida pesquisa? Para isso eu preciso receber um e-mail com os dados abaixo:

 

·         Nome da Empresa

·         Local (Cidade/Estado)

·         Versão do SCSM (Qualquer versão)

 

Encaminhar dados para: contato@clebermarques.com

 

Estas informações não estarão disponíveis em nenhum lugar público, e sim apenas comigo, para fazer em seguida algumas perguntas curtas para você sobre seu ambiente.

 

O objetivo aqui é definir NUMEROS (sem citar publicamente nomes e contatos) para uma futura matéria na revista Canal System Center.

 

Participe, sua colaboração será muito bem vinda!

Abraço.

 

Cleber Marques

Microsoft MVP - System Center Cloud and Datacenter Management
CleberMarques.com | Meu Blog | MOF.com.br | CanalSystemCenter.com.br

Posted by Cleber Marques | with no comments
Filed under: ,

Kaspersky Labs shares a highly advanced new Facebook worm.  This new Javascript based worm can spread from three different browsers (IE, Chrome, and Firefox) providing a cross platform attack.

Facebook - Advanced New LilyJade Cross Platform Worm
http://www.securelist.com/en/blog/706/Worm_2_0_or_LilyJade_in_action

It is quite rare to analyze a malicious file written in the form of a cross-platform browser plugin. It is, however, even rarer to come across plugins created using cross-browser engines. In this post, we will look into a Facebook worm that was written using the Crossrider system – a system still in beta testing.

It uses The Crossrider system, which is intended for writing unified plugins for Internet Explorer (version 7 onwards), Mozilla Firefox 3.5 and Google Chrome. This malicious program is a an excellent example of Malware 2.0-class programs based on modern web technologies, using social networks to propagate themselves and generating illegal incomes for their owners by spoofing various services.

Posted by Harry Waldron | with no comments

A new malicious IM attack is circulating in the Facebook environment, as document by Trend Security

Facebook - New STECKCT worm spreads Instant Messaging
http://blog.trendmicro.com/worm-spreads-via-facebook-private-messages-instant-messengers/

QUOTE:  We recently received reports about private messages found on Facebook and distributing a link, which is a shortened URL pointing to an archive file “May09-Picture18.JPG_www.facebook.com.zip”. This archive contains a malicious file named “May09-Picture18.JPG_www.facebook.com” and uses the extension “.COM”.   Once executed, this malware (detected as WORM_STECKCT.EVL) terminates services and processes related to antivirus (AV) software, effectively disabling AV software from detection or removal of the worm. WORM_STECKCT.EVL also connects to specific websites to send and receive information.

Another noteworthy routine is that this worm downloads and executes another worm, one detected as WORM_EBOOM.AC. Based on our analysis, WORM_EBOOM.AC is capable of monitoring an affected user’s browsing activity such as message posting, deleted posted messages and private messages sent on the following websites such as Facebook, Myspace, Twitter, WordPress, and Meebo. It is also capable of spreading through the mentioned sites by posting messages containing a link to a copy of itself.

Posted by Harry Waldron | with no comments

Nmap is an excellent analytical tool used in the past and the new version 6 has been officially released

https://isc.sans.edu/diary/nmap+6+released/13267

http://nmap.org/6/

QUOTE:  May 21, 2012—The Nmap Project is pleased to announce the immediate, free availability of the Nmap Security Scanner version 6.00 from http://nmap.org/. It is the product of almost three years of work, 3,924 code commits, and more than a dozen point releases since the big Nmap 5 release in July 2009. Nmap 6 includes a more powerful Nmap Scripting Engine, 289 new scripts, better web scanning, full IPv6 support, the Nping packet prober, faster scans, and much more! We recommend that all current users upgrade.

Contents:

  1. About Nmap
  2. Top 6 Improvements in Nmap 6
  3. Press
  4. Screen Shots
  5. Detailed Improvements
  6. Moving Forward (Future Plans)
  7. Acknowledgments
  8. Download and updates

 

Posted by Harry Waldron | with no comments

Summary

The following bulletins have undergone a minor revision increment.
Please see the appropriate bulletin for more details.

  * MS11-100 - Critical
  * MS12-034 - Critical
  * MS12-035 - Critical
  * MS12-MAY

Bulletin Information:

* MS11-100 - Critical

  -http://technet.microsoft.com/security/bulletin/MS11-100
  - Reason for Revision: V1.5 (May 22, 2012): Added entry to the
    update FAQ to announce a detection change for KB2656352 for
    Microsoft .NET Framework 2.0 Service Pack 2 to correct an
    installation issue. This is a detection change only. There were
    no changes to the security update files. Customers who have
    already successfully updated their systems do not need to take
    any action.
  - Originally posted: December 29, 2011
  - Updated: May 22, 2012
  - Bulletin Severity Rating: Critical
  - Version: 1.5

* MS12-034 - Critical

  -http://technet.microsoft.com/security/bulletin/MS12-034
  - Reason for Revision: V1.2 (May 22, 2012): Added an entry to
    the Frequently Asked Questions (FAQ) Related to This Security
    Update section to explain this revision.
  - Originally posted: May 8, 2012
  - Updated: May 22, 2012
  - Bulletin Severity Rating: Critical
  - Version: 1.2

* MS12-035 - Critical

  -http://technet.microsoft.com/security/bulletin/MS12-035
  - Reason for Revision: V2.1 (May 22, 2012): Added entry to the
    update FAQ to announce a detection change for KB2604092 for
    Microsoft .NET Framework 2.0 Service Pack 2 and KB2604110 for
    Microsoft .NET Framework 3.0 Service Pack 2 to correct an
    installation issue. This is a detection change only. There were
    no changes to the security update files. Customers who have
    already successfully updated their systems do not need to take
    any action.
  - Originally posted: May 8, 2012
  - Updated: May 22, 2012
  - Bulletin Severity Rating: Critical
  - Version: 2.1

MS12-MAY

- http://technet.microsoft.com/security/bulletin/MS12-may
- Reason for Revision: V2.1 (May 22, 2012): For MS12-034, added
footnotes for security update KB2660649 for Windows Server 2008
and Windows Server 2008 R2. There were no changes to the
security update files. Customers who have successfully
installed the update do not need to take any action.
- Originally posted: May 8, 2012
- Updated: May 22, 2012
- Version: 2.1

Posted by Don

A MCP Brasil.com está aumentando o seu time de consultoria e, se você tem conhecimentos no System Center Service Manager (SCSM), essa vaga poderá ser sua. Você deve conhecer:

 

• Instalação e configuração do Service Manager, incluindo o Portal e o Data Warehouse

• Criação de fluxos de trabalho

• Personalização de Management Packs

• Criação de relatórios

• Configuração de SLAs e SLOs

• Integração com o AD, SCOM, SCCM e Exchange

 

Se você tiver certificações Microsoft, conhecimento nos outros produtos da família System Center e conhecimento em SQL Server, melhor ainda. Mande já seu CV para cv@mcpbrasil.com colocando a sua pretensão salarial.

 

Obrigado pela leitura e até a próxima publicação,

Abraço.

 

Cleber Marques

Microsoft MVP - System Center Cloud and Datacenter Management
CleberMarques.com | Meu Blog | MOF.com.br | CanalSystemCenter.com.br

Posted by Cleber Marques | with no comments
Filed under: ,

Thanks to everyone who attended my Typemock Isolator and SharePoint session. The links I mentioned were

I will post a link to the recording as soon as it is made available

Posted by But it works on my PC!
Filed under:

Thanks to everyone who attended my Typemock Isolator and SharePoint session. The links I mentioned were

I will post a link to the recording as soon as it is made available

Posted by But it works on my PC!
Filed under:
More Posts Next page »