Tuesday, November 16, 2010

Farm and Citrix servers are not displayed in AMC (Access Manage Console).

I recently updated a 4.5 presentation server in a vmware test farm and server to AMC 4.6.2. After the update, that went without error, the farm and citrix server nodes in access management console were no longer displayed.

I ran the two scripts and the batch file and they worked. The farm showed up first then the presentation server.

After you perform tsteps above you might get a discovery error and see ONLY the farm but not the presentation server (xennapp server). Configure discover and add the servers name into the list for discovery. That will get the server node to appear, the published apps, and everything else. If you keep getting discovery errors, the following is what I did:

I went to configuration tools and removed the current configuration and then exited the console, I started the AMC console again then recreated the configuration. NO more discovery errors.

___________________________________________

Microsoft RDp has increased in usage. it is used by sysm and server admnistrators as much as it's used to connect to desktops for users to access applications remotely, such as RDp with RDS (terminal Services). Admins mostly use it for remote administration of the server in their datacenters but can also access users desktop remotely and control their systems with full remote access to correct as software

Start with adding te printer services role as shown above. This is done through server manager, click on the roles link in the upper right then select (check the box) Print Services . On the next step you can leave the default for most environments. Print server is the only option selected on a default installation of Printer Services on 2008 server.

The migrate print server link shown near the bottom of the first/top image in this post has the following information:
To migrate print servers by using Print Management
- Open the Administrative Tools folder, and then click on Print Management.
- In the Print Management tree pane , right-click on the name of the computer that has the printer queues that you want to export from (this is your source server), and then click Export printers to a file option. This launches the Printer Migration Wizard.
- On the Select the file location page, specify the location to save the printer settings, and then click Next to save the printers.
- Right-click the destination or target computer (this should be your 2008 server, standard or SBS) on which you want to import the printers and have them accessible for your clients, and then click on the Import printers from a file option. This launches the Printer Migration Wizard.
- On the Select the file location page, specify the location of the printer settings file, and then click Next.
- On the Select import options page, specify the following import options:
Import mode. Specifies what to do if a specific print queue already exists on the destination computer.
List in the directory. Specifies whether to publish the imported print queues in the Active Directory Domain Services.
Convert LPR Ports to Standard Port Monitors. Specifies whether to convert Line Printer Remote (LPR) printer ports in the printer settings file to the faster Standard Port Monitor when importing printers.
- Click Next to import the printers.

___________________________________________

Microsoft RDp has increased in usage. it is used by sysm and server admnistrators as much as it's used to connect to desktops for users to access applications remotely, such as RDp with RDS (terminal Services). Admins mostly use it for remote administration of the server in their datacenters but can also access users desktop remotely and control their systems with full remote access to correct as software

Monday, September 27, 2010

The following excerpt is from the Small Business Server 2008 Setup and Migration Help File:

"Password policies in Windows SBS 2008 enforce strong passwords by default, and the password policies dialog in the Windows SBS Console writes the configuration to the default domain policy. The password policy configuration is not written to the Small Business Server Domain Password Policy object, as in Windows SBS 2003. "

The password complextity is a small over-comeable problem that you could encounter during a migration from SBS2003 to SBS2008. The pasword complexity could lead to an even getting logged in the SBS migration and setup logs. The even doesn't tell you it's thecomplexity of the administrator account password, but instead leads you to believe that it the directory services restore mode password that has a problem.The complexity of the pasword required varies depending on the stage of the install. The 2008 SBS server when joining the domain is a client and uses it's own local policy which at this point is no password is required. when joining the domain, it uses the default policy for a domain controller not the policy that is already set for the domain controller in the domain group policy. once in the domain, it will use the policy that has already been established.So, when creating your answer file be sure to have a password complexity matching 8 characters and included uppercase, lower case, a number or a special character (!,@,#,$,%,etc>). If the administrator account that is being used for the migration does not match these characteristics then the migration will fail with and error "FATAL: DcPromo_JoinDomain: The server was not promoted to a domain controller" and an error telling you that "The Directory Services restore Mode password does not meet its complexity criteria" .

BEFORE starting the migration, make the administrator password or the password for the administrator account that will be used for the migration match complexity requirements. I recommend, OVERMATCHING!, or you could be formatting the installation of the new SBS2008 server and trying the migration again. Use 14 characters or more is the main recommended action to over match - that's what I did.