Microsoft | Blog Bujarra.com

Microsoft PowerShell on Windows XP, Windows 2003 and Windows 2008

Windows PowerShell is a new Windows command-line shell that is purpose-built for system administrators. The shell includes an interactive command prompt and scripting environment that can be used independently or together. This shell already comes by default in Windows Server Vista, Windows Server 2008 and logically in the Windows Server edition 2008 Core. But if we want we can also install it on Windows 2003 or Windows XP SP2 If we want information about all the possible commands with Power Shell, it is best to enter the official website and download all the manuals, there are in Spanish: HTTP://www.microsoft.com/windowsserver2008/powershell.mspx If we want to download Power Shell for XP or 2003, We can do it from this website: HTTP://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx being able to choose the x86 or x64 platform we have.

Installing Windows 2008 and Windows 2008 Core

– Instalación nueva de Windows Server 2008 – HERE – Instalación de Windows Server 2008 Core – HERE

Create or join a domain on Windows 2008 + RODC or Read Only Domain Controller,

Create a domain in Windows 2008 – AKI Join a Windows Domain 2008 – AKI Installing a Read-Only Domain Controller – Read Only Domain Controller – RODC – AKI Join a domain using Microsoft Windows 2008 Core (RODC) – HERE

Managing a Windows 2008 Core: Useful commands for configuring and managing a Core

En este documento encontraremos comandos útiles para administrar un servidor Windows Core,

Configuring Terminal Services Web Access – Terminal Services Web Access

We have the possibility to install this component on a Windows server 2008, you don't have to have Terminal Services installed, and is usually installed on the server that has the role of Gateway. This component allows us to connect to applications published on Terminal Servers or to a desktop on a Terminal Services server.

Configuring Terminal Services RemoteApp Manager on Windows 2008

From TS RemoteApp we can configure different applications so that users can use them directly without having to connect to the desktop directly from the servers. They can connect via the web or we can also distribute these applications by generating MSI installation packages, or distribute them from the AD.

Installing the License Server for Terminal Server on Windows 2008

In any organization with Terminal Services servers, a license server must be installed that will be the one that controls how many users/devices connect to the Terminal Services servers. This is a component that needs to be installed on a server on the network, regardless of the components you have installed, and where we will later activate it via the internet/web browser/phone; and then we will install the licenses we have purchased. When we have the server installed and with the licenses purchased, we can generate reports/reports of their use, Consumer Use…

Installing Terminal Services on Windows 2008

En esta parte del documento enseñamos cómo instalar Terminal Services y/o algún componente relacionado, since in the other documents it will be assumed that these services are already installed.

GPO's Group Policies Related to Terminal Server on Windows 2008

This document details all existing policies in Active Directory that directly affect Terminal Services. Each policy and its configuration possibilities are detailed. We will create/edit the policies from the console “Group Policy Management” that is in the “Administrative Tools”.

Configuring Terminal Server Gateway on Windows 2008

Terminal Services on Windows 2008 bring a new feature called “TS Gateway” that we use to connect from outside the organization to computers that use Terminal Server in the local area network. To be able to use this feature, we have to install it on a server on the network, we don't care if you have Terminal Server services installed or not. In the router/firewall we will redirect port 443tcp to this server and this in turn will redirect us to the Terminal Servers securely through 3389tcp, we can also apply certain directives to secure the connection a little more.