Posts
  • LeoPonti Blog

    PowerTip: Use PowerShell to Display a Routing Table

    Summary : Use Windows PowerShell to display your routing table. How can I use Windows PowerShell to display the routing table on my Windows 8.1 laptop? Use the Get-NetRoute function.
  • LeoPonti Blog

    PowerTip: Use PowerShell to Find DNS Suffix Search List

    Summary : Use Windows PowerShell to find a DNS suffix search list. How can I use Windows PowerShell to find how DNS is configured on my computer running Windows 8.1 in terms of domain suffix search lists? Use the Get-DnsClientGlobalSetting function.
  • LeoPonti Blog

    Updates: RAMMap v1.32, Sigcheck v2.01

    RAMMap v1.32 : This fixes a bug in v1.30 that caused RAMMap to fail on Windows 8. Sigcheck v2.01 : This update fixes a bug in the handling of the -u option that sometimes resulted in Sigcheck reporting signed files.
  • LeoPonti Blog

    Update: RAMMap v1.31

    RAMMap v1.31 : This update fixes a bug in v1.30 that caused RAMMap to fail on Windows 8.
  • LeoPonti Blog

    Updates: PsExec v2.0, RAMMap v1.3, Sigcheck v2.0

    PsExec v2.0 : PsExec, a popular utility for executing processes on remote systems, introduces a new option, -r, that specifies the name PsExec assigns to its remote service. This can improve performance when multiple users are interacting concurrently with a system, since each will have a dedicated PsExec service. RAMMap v1.3 : RAMMap, a graphical utility that provides a comprehensive breakdown of physical memory usage by usage type and process, is updated to work on Windows 8.1. Sigcheck v2.0 : This major update to Sigcheck, a command-line file version and digital signature verification utility, adds integration with the VirusTotal antivirus scanner aggregation service. Sigcheck can now check the status of a file against over 40 antivirus engines and launch the associated online VirusTotal report, and even upload files for scanning that have not already been scanned by VirusTotal. This release also reports the machine type of executable images, whether 16-, 32-, or 64-bit.
  • LeoPonti Blog

    Artículos "The Scripting Guys" semana 25/8 al 01/9

    Hola a todos! En esta oportunidad. quiero dejarles la lista de artículos publicados en el Scripting Guy! Blog durante esta semana. Realmente es excelente el trabajo de Ed Wilson!. Weekend Scripter: Creating ACLs for Windows Azure Endpoints—Part 2 of 2 PowerTip: Use PowerShell to Parse Text Files Weekend Scripter: Creating ACLs for Windows Azure Endpoints—Part 1 of 2 PowerTip: Capture Console Application Data with PowerShell Automating DiskPart with Windows PowerShell: Part 5 PowerTip: List Physical Drives with PowerShell Changes to TechNet Library Scripting Node Automating DiskPart with Windows PowerShell: Part 4 PowerTip: Use PowerShell to Get a List of All Volumes Automating DiskPart with Windows PowerShell: Part 3 PowerTip: Show attached USB Drives with PowerShell Automating DiskPart with Windows PowerShell: Part 2 PowerTip: Use PowerShell to Automate Commands with DiskPart Automating DiskPart with Windows PowerShell: Part 1 PowerTip: Find PowerShell Events and Levels Weekend Scripter: Install Free PowerShell Remote Server Admin Tools PowerTip: Use PowerShell to Get BitLocker Recovery Key Espero disfruten de los artículos!! Excelente semana!! Saludos LeoPonti
  • LeoPonti Blog

    Weekend Scripter: Install Free PowerShell Remote Server Admin Tools

    Summary : Microsoft Scripting Guy, Ed Wilson, talks about installing the free Remote Server Administration Tools for Windows PowerShell 3.0 in Windows 8. Microsoft Scripting Guy, Ed Wilson, is here. This morning is an awesome morning. Our friends from Hamburg, Germany have been hanging out all weekend, and it has been a blast. We have spent a bit of time talking about Windows PowerShell training and some of the challenges related to that. We have also shared a love for tea. Yep. It has been a great weekend. Not only that, but the weather also cooperated—it has been sunny and not too humid. One of the first things I do when I build a new computer running Windows 8, is install the Windows 8 Remote Server Administration Tools (RSAT) tools. After I do this, I gain access to many new and useful cmdlets that make it easy to administer everything from Active Directory Domain Services to Windows Software Update Services. Getting the Windows 8 RSAT tools For a free download of the tools, see Remote Server Administration Tools for Windows 8 on the Microsoft Download Center. There are two versions available on the download page: a 32-bit version and a 64-bit version. Finding the actual download is pretty easy—I click the big red Download button that is shown in the following image. I can install the RSAT tools for Windows 8 on computers running Windows 8 or Windows 8 Pro. I cannot install them on my Windows Surface RT, but I can install them on my Windows Surface Pro. The first thing I need to know is if my computer x86 or is it x64. The way that I usually find this out is to query an environmental variable as shown here: PS C:\Users\ed.IAMMRED> $env:PROCESSOR_ARCHITECTURE x86 Before I install the RSAT tools on my computer, I use the following script to to see how many cmdlets and functions are currently on my computer— I have 989. PS C:\Users\ed.IAMMRED> gcm -CommandType cmdlet, function | measure Count : 989 Average : Sum : Maximum : Minimum : Property : So I click the big red Download button to select my appropriate package. Now, I have a choice. I can download the package and install it offline. Or if I choose Run, the file spools to a Temp folder, and it performs the installation from there. This works great if I have good Internet bandwidth, and if I do not anticipate needing to perform the installation again anytime soon. I will open the file, and after a quick security scan...
  • LeoPonti Blog

    PowerTip: Use PowerShell to Get BitLocker Recovery Key

    Use Windows PowerShell to get the BitLocker recovery key. ...( read more )...( read more )
  • LeoPonti Blog

    Deciding How to Use PowerShell to Access AD DS

    Summary : Microsoft Scripting Guy, Ed Wilson, talks about the decision points for deciding how to use Windows PowerShell to access Active Directory Domain Services. Hey, Scripting Guy! I am a bit confused. I see various blogs and scripts on the Script Repository, and some always use a third-party snap-in to access Active Directory Directory Domain Services (AD DS). Others seem to use .NET Framework code to access AD DS, and still others are using a module that looks like it is part of Windows PowerShell. What is the best way to access AD DS? —CB Hello CB, Microsoft Scripting Guy, Ed Wilson, is here. This morning it is actually cool here in Charlotte, North Carolina. In fact, it is way cool because the Scripting Wife found a place on the Internet so she could order some chocolate covered Macadamia nuts. By the way, they go very well with Earl Grey tea with a cinnamon stick. The chocolate, the cinnamon, and the touch of bergamot combine to create an exquisite taste sensation. So, I am out on the lanai sipping tea, nibbling on chocolate covered Macadamia nuts and checking my email on my Surface RT, and I ran across this email to scripter@microsoft.com from CB. Supportability—the big advantage When comparing options for working with Active Directory Domain Services from within Windows PowerShell, one option stands above all the others: supportability. When I use the Active Directory module from Microsoft, it is supported. For me, this means a lot. So if something does not work out perfectly, I know it is supported. I gain access to the Active Directory module in two ways. On a domain controller that is running at least Windows Server 2008 R2, I add the Active Directory management feature, and I have access to the Active Directory module. I can access it locally on the server, or I can use remoting or implicit remoting to access the cmdlets from my workstation. For more information about remoting, see Use PowerShell Active Directory Cmdlets Without Installing Any Software . I can also install the Remote Server Admin Tools (RSAT) on my workstation. The version I install depends on the version of the operating system that I have on my workstation. For more information, see What's Up with Active Directory Domain Services Cmdlets? Note If I install Active Directory Management Service for Windows Server 2008, I do not get access to the Active Directory module on the server. I must install the RSAT tools on my workstation for management...
  • LeoPonti Blog

    PowerTip: Find PowerShell Logging Info

    Summary : Use a Windows PowerShell cmdlet to retrieve logged information about Windows PowerShell. How can I easily find logged information about Windows PowerShell? Use the Get-WinEvent cmdlet and look for a LogName with powershell in the name: Get-WinEvent -LogName *powershell*...( read more )
  • LeoPonti Blog

    PowerShell Workflow for Mere Mortals: Part 5

    Summary : Microsoft Scripting Guy, Ed Wilson, concludes his five-part series about Windows PowerShell Workflow. Hey, Scripting Guy! I have a number of commands that I want to run against several remote servers. The commands include stuff that must happen prior to something else happening. But then, there are also some things that I would like to happen as fast as possible. Is this permissible? If so, do I have to write two different workflows? —TB Hello TB, Microsoft Scripting Guy, Ed Wilson, is here. This afternoon I am sipping an awesome cup of Oolong tea with a cinnamon stick, jasmine flower, and lemon grass. The flavor is just about perfect. In the background, I am listening to Ravel . Outside, the sky is dark and it is raining. The thunder seems to punctuate the music. Note This is the last post in a five-part series about Windows PowerShell Workflow for “mere mortals.” Before you read this post, please read: PowerShell Workflow for Mere Mortals: Part 1 PowerShell Workflow for Mere Mortals: Part 2 PowerShell Workflow for Mere Mortals: Part 3 PowerShell Workflow for Mere Mortals: Part 4 For more information about workflow, see these Hey, Scripting Guy! Blog posts: Windows PowerShell Workflow . Well TB, the good news is that you do not need to write two different workflows to enable parallel processing and sequential processing. Windows PowerShell Workflows are flexible enough to handle both in the same workflow. Adding a sequence activity to a workflow To add a sequence activity to a Windows PowerShell Workflow, all I need to do is use the Sequence keyword and specify a script block. When I do this, it causes the commands in the sequence script block to run sequentially and in the specified order. The key concept here is that a Sequence activity occurs within a Parallel activity. The Sequence activity is required when I want commands to run in a particular order. This is because commands running inside a Parallel activity run in an undetermined order. The commands in the Sequence script block run in parallel with all of the commands in the Parallel activity. But the commands within the Sequence script block run in the order in which they appear in the script block. The following workflow illustrates this technique: workflow get-winfeatures { Parallel { Get-WindowsFeature -Name PowerShell* InlineScript {$env:COMPUTERNAME} Sequence { Get-date $PSVersionTable.PSVersion...
  • LeoPonti Blog

    PowerTip: View PowerShell Console Host Information

    Summary : View Windows PowerShell console host information. How can I easily find information about the Windows PowerShell console host? Use the Get-Host cmdlet, and select the RawUI property from the InterhostUserInterface object: (get-host).ui.RawUI...( read more )
  • LeoPonti Blog

    PowerShell Workflow for Mere Mortals: Part 4

    Summary : Microsoft Scripting Guy, Ed Wilson, continues his five-part series about Windows PowerShell Workflow. Hey, Scripting Guy! Yesterday you talked about Windows PowerShell Workflow activities. But you only demonstrated the Parallel activity. Is there something you can share with me about some of the other types of activities? In particular I am interested in checkpoints because I think they can help me. —AP Hello AP, Microsoft Scripting Guy, Ed Wilson, is here. This morning, it is really foggy outside. To be honest, it seems to look more like fall than the end of summer. But then, I am not a real weather person—I don’t even play one on TV. It is fairly humid and fairly cool—a nice morning for a cup of English Breakfast tea. I am not in the mood to experiment today, and so I am going with a standard recipe of mine: Three scoops of English Breakfast tea, a scoop of lemon grass, and a single crushed cinnamon stick. I let it steep for three minutes and 45 seconds, grab my tea pot, my Surface RT, and head outside to check email. AP, you want to talk about checkpoints in a Windows PowerShell workflow today. No problem… Note This is the fourth in a five-part series of blog posts about Windows PowerShell Workflow for “mere mortals.” Before you read this post, please read: PowerShell Workflow for Mere Mortals: Part 1 PowerShell Workflow for Mere Mortals: Part 2 PowerShell Workflow for Mere Mortals: Part 3 For more information about workflow, see these Hey, Scripting Guy! Blog posts: Windows PowerShell Workflow . Checkpoints Windows PowerShell workflow If I have a Windows PowerShell Workflow, and I need to save the workflow state or data to a disk while the workflow runs, I can configure a checkpoint. In this way, if something interrupts the workflow, it does not need to restart completely. Instead, the workflow resumes from the point of the last checkpoint. Setting a checkpoint in a Windows PowerShell Workflow is sometimes referred to as “persistence” or “persisting a workflow.” Because Windows PowerShell Workflows run on large distributed networks, or they control the execution of long running tasks, it is vital that the workflow can handle interruptions. Understanding checkpoints A checkpoint is a snapshot of the workflow’s current state. This includes the current values of variables and generated output. A checkpoint persists this data to...
  • LeoPonti Blog

    PowerTip: Use PowerShell to Display Date, Time, and Hour

    Summary : Use Windows PowerShell to display date, time, and hour in 24-hour format. How can I use Windows PowerShell to get the hour of the day in 24-hour format? Use the Get-Date cmdlet and specify the “%H” pattern to the UFormat parameter ( H is case sensitive): get-date -UFormat "%H"...( read more )
  • LeoPonti Blog

    PowerShell Workflow for Mere Mortals: Part 3

    Summary : Microsoft Scripting Guy Ed Wilson continues his five-part series about Windows PowerShell Workflow. Hey, Scripting Guy! So what’s up with Windows PowerShell workflows and activities? I do not know what an activity is. Can you help me? —CJ Hello CJ, Microsoft Scripting Guy, Ed Wilson, is here. Ah…this afternoon, I am sipping a cup of Darjeeling Earl Grey tea with a bit of cinnamon stick, and I added just a bit of lavender honey from a nearby lavender farm. I am accompanying my tea with a 90% cocoa bar with black currants and hazelnuts. The combination is absolutely stunning. Note This is the third in a five-part series of blog posts about Windows PowerShell Workflow for “mere mortals.” Before you read this post, please read: PowerShell Workflow for Mere Mortals: Part 1 PowerShell Workflow for Mere Mortals: Part 2 For more information about workflow, see these Hey, Scripting Guy! Blog posts: Windows PowerShell Workflow . Workflow activities A Windows PowerShell Workflow is made up of a series of activities. In fact, the basic unit of work in a Windows PowerShell Workflow is called an activity. There are five types of Windows PowerShell Workflow activities that are available for use. The following table describes the types of activities. Activity Description CheckPoint-Workflow (alias = PSPersist) Takes a checkpoint. Saves the state and data of a workflow in progress. If the workflow is interrupted or rerun, it can restart from any checkpoint. Use the Checkpoint-Workflow activity along with the PSPersist workflow common parameter and the PSPersistPreference variable to make your workflow robust and recoverable. ForEach -Parallel Runs the statements in the script block once for each item in a collection. The items are processed in parallel. The statements in the script block run sequentially. Parallel Allows all statements in the script block to run at the same time. The order of execution is undefined. Sequence Creates a block of sequential statements within a parallel script block. The Sequence script block runs in parallel with other activities in the Parallel script block. However, the statements in the Sequence script block run in the order in which they appear. Sequence is valid only within a Parallel script block. Suspend-Workflow ...
  • LeoPonti Blog

    PowerTip: Customize How PowerShell Displays a Date

    Summary : Easily customize the way Windows PowerShell displays a date. How can I use Windows PowerShell to easily display the date as day-dash-month-dash-four-digit year? Use the Get-Date cmdlet,specify a custom format by using the Format parameter, and use dd for the date, M for the month and yyyy for a four-digit year (this is case sensitive): Get-Date -Format "dd-M-yyyy"...( read more )
  • LeoPonti Blog

    PowerShell Workflow for Mere Mortals: Part 2

    Summary : Microsoft Scripting Guy, Ed Wilson, continues a five-part series about Windows PowerShell Workflow. Hey, Scripting Guy! So Windows PowerShell Workflow seems pretty cool. But I am wondering if it is possible to use it to easily provide workflow types of things for remote computers? Is this possible? —BB Hello BB, Microsoft Scripting Guy, Ed Wilson, is here. We are enjoying a cool stretch of weather here in Charlotte, North Carolina. In fact, we have the windows open. We are also enjoying our visiting friends from Hamburg, Germany. So not only do we have great weather, but we have great company. Note This is the second in a five-part series of blog posts about Windows PowerShell Workflow for “mere mortals.” You should read PowerShell Workflow for Mere Mortals: Part 1 before you read this post. For more information about workflow, see these Hey, Scripting Guy! Blog posts: Windows PowerShell Workflow . Parallel Windows PowerShell One of the reasons for using a Windows PowerShell Workflow is to be able to easily execute commands in parallel. This can result in some significant time savings. Note For an example of the time savings that are possible by using a Windows PowerShell Workflow and running commands in parallel, see the excellent post written by Windows PowerShell MVP, Niklas Goude, Use PowerShell Workflow to Ping Computers in Parallel . To perform a parallel activity by using Windows PowerShell Workflow, use the Foreach keyword with the –Parallel parameter. This is followed by the operation and the associated script block. The following script illustrates this technique: Foreach -Parallel ($cn in $computers) { Get-CimInstance -PSComputerName $cn -ClassName win32_computersystem } One of the things to keep in mind (as a major source of early frustration) is that when I call the Get-CimInstance cmdlet from within the script block of my parallel Foreach keyword, I have to use the automatically added PSComputerName parameter, not the ComputerName parameter I would normally use with the cmdlet. This is because this is the way that Windows PowerShell Workflow handles computer names. If I look at the command-line syntax for Get-CimInstance , I do not see the ––PSComputerName parameter at all. The nice thing is that if I forget to use –PSComputerName , and I try to run the Windows PowerShell Workflow, an error message appears. The message is detailed enough that it actually...
  • LeoPonti Blog

    WikiNinjas Blog: Semana del 12/8 al 19/8

    Hola a todos! En esta oportunidad, les dejo los artículos que fueron publicados en la semana del 12/8 al 19/8 en el blog de TechNet WikiNinjas 19/8 Interview with a Wiki Ninja and SharePoint Guru - Matthew Yarlett Por Ed Price 19/8 July Small Basic Guru - Nonki Takahashi's "Shapes Editor" Por Ed Price 18/8 Training Needs Analysis - Trainer to Trainer Por Serhad MAKBULOĞLU 18/8 Top Contributors Awards! Special Steef-Jan, Gokan & Sandro edition :D Por XAML guy 17/8 July SharePoint Guru - Matthew Yarlett brings us "SharePoint 2010: Viewing, Sorting, and Filtering SharePoint User Profiles Using PowerShell" Por Ed Price 16/8 Friday with International Community Update – Articles about BizTalk Server 2010 and 2013 from Holland Por Luciano Lima [MVP] Brazil 15/8 TechNet Wiki - Enter the International Council Por Ed Price 14/8 Wiki Life: What content is not appropriate for our wiki Por Horizon_Net 13/8 July BizTalk Guru - Steef-Jan brings us "Provisioning BizTalk Services using the Windows Azure Management Portal" Por Ed Price 13/8 TNWiki Article Spotlight - Directory Services Por LeoPonti 12/8 Interview with a Wiki Ninja: Carmelo La Monica - Community Contributor in C#, VB.NET, LINQ, Windows 8 apps, and Windows Phone 8 apps Por Ed Price 12/8 Interview with a Wiki Ninja: Lex Hegt Por Sandro Pereira Espero que disfruten de estos artículos y esta semana, se vienen muchos mas... :=) Saludos! LeoPonti
  • LeoPonti Blog

    PowerTip: Use PowerShell to Display Locale-Specific Date

    Summary : Learn how to use Windows PowerShell to display the date in locale-specific format. How can I use Windows PowerShell to display the day, month, and two-digit year in locale specific format? Use the Get-Date cmdlet and the –uformat parameter: get-date -UFormat %x...( read more )
  • LeoPonti Blog

    PowerShell Workflow for Mere Mortals: Part 1

    Summary : Microsoft Scripting Guy, Ed Wilson, begins a five-part series about Windows PowerShell Workflow. Hey, Scripting Guy! What is up with Windows PowerShell Workflow? Everyone acts like it is some deep, dark mystery—similar to trying to understand neutrinos . So come on…it is Windows PowerShell, so how hard can it be? —MD Hello MD, Microsoft Scripting Guy, Ed Wilson, is here. This week I am going to address some questions and comments that have been collecting about Windows PowerShell Workflow. I like using Windows PowerShell Workflow because it offers a number of significant capabilities that help solve rather interesting issues. Note This is the first in a five-part series of blog posts about Windows PowerShell Workflow for “mere mortals.” For more information, see these Hey, Scripting Guy! posts about Windows PowerShell Workflow . For a conceptual introduction, see When Windows PowerShell Met Workflow . Why use workflows Windows PowerShell Workflows are cool because the commands consist of a sequence of related activities. I can use a workflow to run commands that take an extended period of time. By using a workflow, my commands can survive reboots, disconnected sessions. They can even be suspended and resumed without losing the data. This is because the workflow automatically saves state and data at the beginning and at the end of the workflow. In addition, it can use specific points that I specify. These persistence points are like checkpoints or snapshots of the activity. If a failure occurs that is unrecoverable, I can use the persisted data points, and then resume from the last data point instead of having to begin the entire process anew. Note Windows PowerShell Workflow is Windows Workflow Foundation. But instead of having to write the workflow in XAML, I can write the workflow by using Windows PowerShell syntax. I can also package the workflow in a Windows PowerShell module. For detailed documentation, see Windows Workflow Foundation . The two main reasons to use Windows PowerShell Workflow are reliability and performance when performing large scale or long-running commands. These reasons break down into the following key points: Parallel task execution Workflow throttling Connection throttling Connection pooling Integration with disconnection sessions Workflow requirements I can run a workflow that uses Windows PowerShell cmdlets if the target (the managed...
  • LeoPonti Blog

    Script - Export completo de Subnets por Site en nuestro Forest

    Hola a todos! En esta oportunidad, quería dejarles un Script muy interesante, el cual nos permite exportar en pocos segundos, el detalle de las subnets que tenemos en cada uno de nuestros Site del Forest donde necesitemos tener dicho detalle, de estar en una estructura pequeña, no tendrías problemas ni nos demandaría mucho tiempo realizar dicha tarea en forma manual, pero tengan en cuenta ante ambientes muy grandes, que sería de mucho tiempo de trabajo, tener la información exportada en un archivo. Este detalle nos puede server como inventario o también para realizar un análisis de como tenemos configurado nuestro Site&Services en cuanto a las subnets a que sitio pertenecen, recuerden que tener bien configurado esta parte, hará que las autenticaciones, sean validadas en el sitio local o más cercano de donde está el equipo que el usuario quiere acceder, evitando inconvenientes de lentitud innecesarios.- Entonces, descargando el archivo *.vbs desde: Link subido a Microsoft TechNet Gallery y guardarlo como list_subnets.vbs y luego, desde línea de comando, nos posicionamos en el directorio donde guardamos el archivo vbs y ejecutamos cscript list_subnets.vbs > export_subnets.txt y en el archivo *.txt que detallamos, nos exportara el detalle de Site y que Subnets están declaradas en el mismo, toda información correspondiente al Forest que pertenece el equipo desde donde corrimos el script. El archivo export_subnets.txt resultante, tendrá un formato similar a como les detallo a continuación: Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. SITIO1,10.1.10.0/24,10.1.19.0/24,10.1.20.0/24,10.1.27.0/24,10.1.29.0/24,10.1.59.0/24,10.1.60.0/24, 10.1.67.0/24,10.113.33.0/24 SITIO2,10.1.12.0/24,10.1.44.0/24,10.1.6.0/24,10.10.44.0/24,10.11.44.0/24,10.13.44.0/24,10.29.0.0/21, 10.29.4.0/24,10.3.11.0/24,10.3.44.0/24 SITIO3,10.1.22.0/24,10.1.57.0/24,10.1.7.0/24,10.11.7.0/24,10.113.12.0/24,10.113.13.0/24,10.113.27.0/24, 10.113.37.0/24,10.114.12.0/24 SITIO4,10.1.33.0/24,10.1.38.0/24,10.1.4.0/22,10.1.9.0/24,10.10.33.0/24,10.101.0.0/20,10.11.32.0/22, 10.111.1.0/24,10.112.0.0/24 SITIO5,10.1.93.0/24,10.2.93.0/24,10.3.92.0/22,10.4.93.0/24,10.65.93.0/24,10.66.93.0/24,10.67.93.0/24, 10.68.93.0/24,10.69.93.0/24 SITIO6,10.100.42.0/24,10.113.34.0/24,10.113.43.0/24,10.113.44.0/24,10.113.62.0/24 SITIO7,10...
  • LeoPonti Blog

    Redireccionando contenedor default de objetos Computers en AD

    Hola a todos! En esta oportunidad, les quiero dejar como redireccionar el contenedor default donde quedan los objetos Computers al generarse cuando se hace el Join de los equipos a nuestro dominio, como ventaja principal para realizar esta tarea, es cuando queremos desde un principio, aplicar políticas de dominio a nuestros equipos apenas los pongamos en dominio, sin esperar a que los objetos sean movidos de OU después de un tiempo. En el Contenedor "Computers" donde por default en un dominio que instalamos y no realizamos el cambio, es donde se generan los objetos Computers al realizar el Join de los mismos y donde no podemos adjuntar una GPO de Dominio, con lo cual, muchos optan por correr el comando que les quiero dejar y ahí si, en la nueva OU que direccionamos, podremos poner una GPO de dominio y aplicar configuraciones para que apliquen desde un principio en los equipos que adjuntamos a nuestro dominio. Como comentario inicial, este comando se corre por dominio, con lo que si tenemos varios dominios donde queremos realizar este cambio, por más que los mismos correspondan a un único Forest, tendremos que correrlo en cada uno de los dominios que deseamos modificar.- Para empezar, entraremos a nuestra Consola de administración de Usuarios y Computadoras, para lo cual, tenemos que estar trabajando desde un Domain Controller o desde un equipo donde tengamos en Windows Server 2003 o Windows XP las Herramientas Administrativas de Active Directory o en Windows Server 2008 o Superior, el Feature de Administración instalado. Luego hacemos Start – Administrative Tools – Active Directory Users and Computers como se muestra en la siguiente pantalla: También podemos abrir la consola, desde Start - Run - Poniendo la llamada a la consola dsa.msc Donde en la consola, podremos ver el contenedor Default de cualquier implementación de Active Directory donde se generan los objetos "Computer" al realizar el join al dominio, ese contenedor, se llama "Computers": Ahora para realizar el cambio, generaremos una nueva OU que este directamente desde el raíz del dominio, para lo cual, nos pondremos en el dominio, desplegamos el menu y hacemos New - Organizational Unit como se muestra a continuación: Donde nos aparecerá una ventana de creación y pondremos el nombre de la OU que deseamos generar, en este caso, pondremos "NewComputers" Al dar...
  • LeoPonti Blog

    Redireccionando contenedor default de objetos Users en AD

    Hola a todos! En esta oportunidad, les quiero dejar como redireccionar el contenedor default donde quedan los objetos Users al generarse cuando desde una aplicación, se generan cuentas y se deja al dominio que las genere en un contenedor por defecto. En el Contenedor "Users" donde por default en un dominio que instalamos y no realizamos el cambio, es donde se generan los objetos Users.- Como comentario inicial, este comando se corre por dominio, con lo que si tenemos varios dominios donde queremos realizar este cambio, por más que los mismos correspondan a un único Forest, tendremos que correrlo en cada uno de los dominios que deseamos modificar.- Para empezar, entraremos a nuestra Consola de administración de Usuarios y Computadoras, para lo cual, tenemos que estar trabajando desde un Domain Controller o desde un equipo donde tengamos en Windows Server 2003 o Windows XP las Herramientas Administrativas de Active Directory o en Windows Server 2008 o Superior, el Feature de Administración instalado. Luego hacemos Start – Administrative Tools – Active Directory Users and Computers como se muestra en la siguiente pantalla: También podemos abrir la consola, desde Start - Run - Poniendo la llamada a la consola dsa.msc Donde en la consola, podremos ver el contenedor Default de cualquier implementación de Active Directory donde se generan los objetos "User", ese contenedor, se llama "Users": Ahora para realizar el cambio, generaremos una nueva OU que este directamente desde el raíz del dominio, para lo cual, nos pondremos en el dominio, desplegamos el menu y hacemos New - Organizational Unit como se muestra a continuación: Donde nos aparecerá una ventana de creación y pondremos el nombre de la OU que deseamos generar, en este caso, pondremos "NewUsers" Al dar OK , veremos la OU ya generada en la consola de Users and Computers, para también seguir, es importante ir desde la consola, View - Advanced Features : Ahora desde la nueva OU, desplegaremos el menu, y vamos a "Properties", en la nueva ventana que nos aparece, vamos a la solapa "Attribute Editor" y de la lista de atributos que aparecen, vamos al atributo "distinguishedName", donde daremos la opción "View" y copiaremos la información que tenga dicho atributo. Una vez realizado el paso anterior, vamos a Start - Command Prompt el cual ejecutaremos como...
  • LeoPonti Blog

    Version de Schema en nuestro Forest

    Hola a todos! En esta oportunidad, quiero dejarles las formas en las que podemos chequear la versión de nuestro Schema de Active Directory, esto identificará la versión de Sistema Operativo de nuestros Domain Controllers, no en general, ya que con eso lo identificamos viendo el Functional Level de nuestra estructura, pero si sabremos que al menos un Domain Controller de nuestra infraestructura, es de la versión de nuestro Schema, ya que para promover un Domain Controller con una versión de Sistema Operativo superior, si o si tenemos que realizar un upgrade o extender nuestro Schema del Forest.- Las versiones de Schema hasta el momento y a que versión de Sistema Operativo corresponden, son las siguiente: * 13 - Windows 2000 Server * 30 - Windows Server 2003 * 31 - Windows Server 2003 R2 * 44 - Windows Server 2008 * 47 - Windows Server 2008 R2 * 51 - Windows Server 8 Developers Preview * 52 – Windows Server 8 Beta (Disponible al público) * 56 - Windows Server 2012 Si bien tenemos scripts y otras herramientas para chequear la versión de nuestro Schema, a mi en este post me gustaría identificar cuatro formas: 1) Mediante dsquery . 2) Mediante consola de adsiedit . 3) Mediante consola de ldp . 4) Mediante clave de registro ( regedit ). 1) Mediante dsquery: Desde un Domain Controller o equipo perteneciente al dominio, teniendo las herramientas administrativas o el features de administración de Active Directory, ejecutaremos la línea de comando mediante un CMD. En donde ejecutaremos la siguiente linea de comando: dsquery * cn=schema,cn=configuration,dc=leoponti,dc=net -scope base -attr objectVersion Donde "dc=leoponti,dc=net" corresponde a las referencias del Forest que tengan cada uno de ustedes, en mi caso el laboratorio aplica a un distinguishedname "dc=leoponti,dc=net" Al ejecutarlo, nos dara la versión que tengamos en cada una de las estructuras según se muestra a continuación: 2) Mediante consola de adsiedit. Desde un Domain Controller o equipo perteneciente al dominio, teniendo las herramientas administrativas o el features de administración de Active Directory, ejecutaremos dentro de las herramientas administrativas, la consola ADSIEdit: En la parte superior izquierda de la consola que se nos abrirá, en la opcion ADSI Edit , desplegamos el menu y seleccionamos "Connect to", donde nos aparecera...
  • LeoPonti Blog

    Windows Server 2012 - Generando Disco USB Booteable

    Hola a todos! En esta oportunidad, quiero compartir con ustedes una forma sencilla de hacer un dispositivo USB booteable con Windows Server 2012, de esta misma forma, también se puede hacer con Windows Server 2008R2, Windows 7 y Windows 8.- Para comenzar, tenemos que descargar la Herramienta Windows 7 USB/DVD Tool desde Microsoft Store Online: http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool Una vez que se descarga el instalador, corremos la instalación del mismo, para lo cual, tenemos que tener instalado previamente .NET Framework 3.5, si no lo tenemos instalado, nos aparecerá un aviso de descargo e instalarlo como se muestra a continuación: Donde vamos a “Download and install this feature” para procederá la instalación de .NET Framework 3.5 Cuando finalice la instalación de .NET Framework, nos aparecerá el aviso como se muestra a continuación: Al darle "Close", si comenzaremos la instalación de la Tool que necesitamos para poder realizar el dispositivo USB Booteable: Aceptando la pantalla de bienvenida, daremos la opcion "Next": Al dar la opcion "Install", comenzará el proceso de instalación. Dando Finish, se cerrará la instalacion habiendo finalizado la misma. Ahora ejecutaremos la Tool desde el icono que nos apareció en el escritorio. Donde nos aparecerá la siguiente ventana dando comienzo al wizard para generar el dispositivo booteable. Donde iremos a “Browse” y seleccionamos la ISO de Windows Server 2012 que previamente hayamos descargado desde la Web de Microsoft y tengamos localmente en nuestro disco. Daremos NEXT y nos apareceran las siguientes posibilidades. Start over: Volveremos a la pantalla para cargar en la Tool, la imagen ISO de nuestro Sistema Operativo Windows Server 2012. USB Device: Seguiremos la Tool para generar el disco booteable con un dispositivo USB. DVD: Seguiremos la Tool para generar el disco booteable con nuestra unidad de DVD. En nuestro caso, seleccionaremos la opción USB device para seguir nuestro wizard. Luego de confirmar la unidad con el dispositivo USB, daremos "Begin copying" para comenzar el proceso de dar format al dispositivo y posterior copia en el dispositivo y configurarlo como booteable. Luego de dar el formato, comienza la copia de archivos: Una vez que...
Page 2 of 6 (126 items) 12345»