La vostra fonte migliore delle informazioni e delle notizie circa finestre Vista, segreti e Fissaggi del Vista sul Internet

ARTICOLI del Vista PRINCIPALE 50 Vista VIDEOS Vista MOLLE AIUTO del Vista

Autori dell'ospite

Attualmente state passando in rassegna gli articoli da Software compatibile di MS Windows Vista abbinare la categoria Autori dell'ospite.

Transitioning dallo scambio 2000 a 2007 (parte 3)

Ora dopo il controllo dei componenti interi di predisposizione per istallazione, se iniziamo la messa a punto noi otterrà alcuni messaggi di errore come questo:


La messa a punto ha incontrato un problema mentre convalidando il dichiarare dell'indice attivo: La versione del sistema operativo del regolatore di dominio è 5.0 (2195) pacchetti 4 di servizio. La versione minima richiesta è 5.2 (3790) pacchetti 1 di servizio.


Ciò un'edizione comune realmente, il motivo dietro questa è che la messa a punto sta controllando tutto il DCs che debbano essere 2003 sp1 così come il GCs, a causa di quello che dobbiamo indicare la messa a punto alla CC specifica 2003. Questa edizione sarà riparata nello scambio 2007 sp1. Così, sto andando iniziare la messa a punto in un modo incustodito che comincia vicino preparare la foresta facendo funzionare gli interruttori accennati precedentemente ma con specificare /dc: parametro a punto alla CC 2003 delle finestre. La prima cosa che dobbiamo fare nello scambio schierante 2007 in un'organizzazione di scambio dell'eredità è di funzionare

Setup.com /PrepareLegacyExchangePermissions

•Dopo che dobbiamo preparare lo schema, questo può essere fatto facendo funzionare il seguente ordine


Setup.com /PrepareSchema /dc:NameofWindows2003DC

Rediga l'ANNUNCIO, scrivendo l'ordine a macchina:


Setup.com /PrepareAD /dc:NameofWindows2003DC

Nota: potete fare funzionare l'ordine di Setup.com /PrepareAD prima del funzionamento /PrepareLegacyExchangePermissions e del /PrepareSchema, questo farà funzionare /PrepareLegacyExchangePermissions e /PrepareSchema comanda automaticamente.

Ora possiamo iniziare la messa a punto, ma dobbiamo iniziare la messa a punto in un modo incustodito come noi abbiamo detto, unendo una coppia degli interruttori con l'ordine di messa a punto, secondo i vostri bisogni:


messa a punto /m: Installi /roles: M., HT, C, LA TA /dc:

...
Scatti per continuare a leggere “Transitioning dallo scambio 2000 a 2007 (parte 3)„

Scritto da rodney.buike sopra 1° ottobre 2007 con nessun osservazioni.
Legga più articoli sopra Assistente di scambio e Autori dell'ospite.

Transitioning dallo scambio 2000 a 2007 (parte 2)

Prima che otteniamo cominciati con l'installazione dello scambio 2007 è suggerito ora per fare funzionare l'ultima versione degli attrezzi dell'analizzatore di pratica migliori di scambio e sceglie il controllo 2007 di prontezza di scambio, nel mio caso, l'attrezzo mi ha fatto il seguente rapporto:

Così, la mia organizzazione di scambio è nel modo mixed, esso deve essere cambiata al modo natale. Generalmente, ci sono tre requisiti preliminari che devono controllato prima dell'installazione dello scambio 2007, sono:

  • Foresta attiva dell'indice:
    • il livello di funzionalità di dominio deve essere assistente 2003 di Windows o del Windows 2000
    • the domain controller that is the schema master is running Windows Server 2003 SP1 or higher
    • the Global Catalog server is running Windows Server 2003 SP1 or higher


There are some switches that you can run them to prepare the environment by preparing the permission required for exchange 2007, preparing the schema, preparing active directory, and preparing domain. Those switches are:


Setup.com /PrepareLegacyExchangePermissions
Setup.com /PrepareSchema
Setup.com /PrepareAD
Setup.com /PrepareDomain or Setup.com /PrepareAllDomains


Note: you can run the 32-bit version of Exchange 2007 from the trial CD to prepare you environment.

  • Exchange organization
    • it is a must to run the exchange organization in native mode
    • because of this all Exchange servers running Exchange 5.5 or earlier must be removed

In my case I have to change the organization mode simply by opening the exchange system manager, right click exchange organization, choose properties then choose the change mode button you will get a warning message, click yes, as simple as that.

Server requirements:

  • .Net framework 2.0
  • Update KB926776

...
Click to continue reading "Transitioning from Exchange 2000 to 2007 (Part 2)"

Written by rodney.buike on September 28th, 2007 with no comments.
Read more articles on Exchange Server and Guest Authors.

Using Certificates with Compaq/HP RILOE and ILO Hardware

Here is another great guest post from: Jason Boche, MCSE NT4/2000/2003, MCSA 2000/2003, MCP, VCPx2, CCA, A+

If you have used Compaq/HP brand server hardware, you are most likely familiar with RILOE boards (Remote Insight Lights Out Edition) and ILO boards (Integrated Lights Out). These are hardware devices that provide remote access to Compaq/HP server hardware. A key benefit is their "out of band" management attribute, meaning they operate independent of the server's native host operating system, network, and CPU. They've got their own CPU, memory, and a built in web server which listens on ports 80 and 443 and serves as the configuration and management tool. Another benefit is the encrypted traffic that passes along the wire between RILOE/ILO and the client web browser which is accessing it. By default, this traffic is passed on TCP port 443. If you've used the RILOE/ILO before, you are probably used to seeing the following all too familiar screen:

The underlying reason for this is that your client knows nothing about the certificate authority from which the certificate for the RILOE/ILO was generated, other than it is not trusted. This is no cause for alarm as long as you trust the Hewlett Packard company from Houston, TX, however, failure to address this will cost you an extra mouse click each and every time you access this or any other RILOE/ILO on your network. Considerably more harmful is the numbing effect this screen will cause for each administrator who is

...
Click to continue reading "Using Certificates with Compaq/HP RILOE and ILO Hardware"

Written by daniel.nerenberg on June 11th, 2007 with no comments.
Read more articles on Guest Authors.

Guest Post: Script to install and manage virtual CD / DVD drives

This great article come from Michael Khanin (MCP, MCP+I, CNA, CNE, MCSE) who also blogs on his blog site http://TheSystemAdministrator.com

Recently there was a necessity to install a Virtual CD/DVD on many computers on the same network. And it was necessary, that the virtual CD/DVD would be set to a special letter in the system. Right now there are a lot of programs which emulate CD/DVD and can mount any CDs/DVD images, as I wished to make all installation and configuration run remotely (well laziness by me, not wanting to run from computer to computer) It was necessary for the program to install in silent mode. After a quick search I chose МagicDisc.

I've selected this program for several reasons:

1. The program is free-of-charge (but not all options work in the free-of-charge version, but what is necessary for me, works)

2. There is opportunity to run setup in silent mode.

3. It is possible to operate all necessary functions from a command line.

For a more satisfiying management experience from the command line one more file, Miso.exe is required.

The given file can be found on the МagicDisc site.

For the installation I have written a script, INSTALL-V-CD.bat.

INSTALL-V-CD.bat is very simple and contains just one line:

setup_magicdisc.exe /S

To start the script on a remote system I used psexec.exe which can be downloaded here.

After the installation of МagicDisc, it was necessary to copy miso.exe to the remote computer. It is important to note that miso.exe should be located in a directory which is registered in the system PATH.

Now the most interesting part. We create virtual a CD

...
Click to continue reading "Guest Post: Script to install and manage virtual CD / DVD drives"

Written by daniel.nerenberg on June 5th, 2007 with no comments.
Read more articles on Guest Authors.

Guest Post: Providing a Default Domain for Microsoft FTP User Authentication

Providing a Default Domain for Microsoft FTP User Authentication

Jason Boche, MCSE NT4/2000/2003, MCSA 2000/2003, MCP, VCPx2, CCA, A+

As usual, I have a story behind most of my experiences. If you’re not interested in reading about it, skip to the section “How to do it”.

I’ve been using FTP servers since I learned how to write and publish web pages in HTML – about the early to mid 1990’s. I found using an FTP client to connect to an FTP server was pretty straight forward. The three required elements to provide are a host name, a user name, and a password. Sure, there are additional parameters that can be provided such as configuring a connection through a firewall, changing ports, or providing local and remote working directories, but let’s keep it simple, because that’s what this article is about – keeping it simple for end users who are not as technical, and would like to keep it that way.

Fast forward a few years. Now I’ve got fast ADSL broadband internet connectivity, as many static IP addresses as I want through my local ISP (static IPs still weren’t a hot commodity to be cherished back then), and servers in my spare bedroom running Microsoft IIS and FTP, as well as domain controllers. I decided that I’ve got more than enough bandwidth to host some websites for friends and small businesses in the area. These customers are not technically savvy. They’ve put together a website using some do-it-yourself WYSIWYG tool

...
Click to continue reading "Guest Post: Providing a Default Domain for Microsoft FTP User Authentication"

Written by daniel.nerenberg on June 4th, 2007 with no comments.
Read more articles on Guest Authors.