Enable PowerShell ISE on Server 2008

PowerShell ISE is GUI utility which allows us to create, test, debug powershell scripts is graphical mode. Powershell ISE is installed on Windows 7 by default. But we need to enable Powershell ISE on Server 2008 by following these steps:

1. Launch PoserShell and run thse command: 
    Import-Module ServerManager 
    
Add-WindowsFeature PowerShell-ISE

image

PowerShell ISE has been installed on Server 2008.

Interview questions for SCCM 2007

Question: What is SMS provider and what it does.=
Answer: The SMS Provider is a WMI provider that allows both read and write access to the Configuration Manager 2007 site database. The SMS Provider is used by the Configuration Manager console, Resource Explorer, tools, and custom scripts used by Configuration Manager 2007 administrators to access site information stored in the site database. The SMS Provider also helps ensure that Configuration Manager 2007 object security is enforced by only returning site information that the user account running the Configuration Manager console is authorized to view. More on SMS provider…

Question: Can we upgrade SCCM secondary site to primary site?
Answer: Yes we can do. More on upgrading secondary sites…..

Question: Can you change a secondary site to a primary site?
Answer:  No. A secondary site is always a secondary site. It cannot be upgraded, moved, or changed without deleting it and reinstalling it. If you delete and reinstall, you lose all secondary site data.

Question: Can you distribute a package to a computer without making it a member of a collection?
Answer:  No. To distribute software you must have a package, a program and an advertisement. Advertisements can only be sent to collections, not to computers. If you want to distribute a package to a single computer, you must create a collection for that computer.

Question: Can a site have more than one default management point?
Answer:  No. You can configure more than one management points in a site, but only one of those management points can be configured as the default management point to support intranet clients in the site. If you are concerned about performance, you can configure more than one management point, configure them to be part of a Network Load Balancing (NLB) cluster, and them configure the NLB cluster as the default management point.

Question: Can a secondary site have child sites?
 Answer: No. A secondary site cannot have a primary or secondary site reporting to it. Secondary sites are always child sites to a primary site.

Question: Can you install the Configuration Manager client components without discovering the computer first?
Answer: Yes. Client Push Installation is the only client installation method that requires clients to be discovered first.

Question: Does Configuration Manager 2007 mixed mode require a public key infrastructre (PKI)?
Answer:  No. Configuration Manager 2007 native mode requires a PKI, but Configuration Manager 2007 does not. PKI authentication helps provide a greater level of security, but Configuration Manager 2007 does not help you install or configure the PKI infrastructure. If you do not already have the expertise to install and configure the PKI infrastructure, you can start with mixed mode and then change to native mode later.

Question: Can computers show up in the Configuration Manager console before they have the Configuration Manager client installed?
Answer:  Yes. If you use a discovery method, Configuration Manager can find many resources and create data discovery records (DDRs) for them, and those DDRs are stored in the database. However, you cannot use Configuration Manager features such as software distribution, software updates management, and inventory until you install the client components.

Question: Can you assign clients to a secondary site?
Answer:  No.If you have a secondary site, the client must be assigned to the primary parent of the secondary site. However, Configuration Manager knows how to manage clients at the child secondary site. If there is a distribution point at the secondary site that has the content the clients need, the clients will probably get the content from the local distribution point instead of crossing the WAN link to the primary site.

Question: Can Configuration Manager 2007 be used to package software for distribution?
Answer:  No. Configuration Manager 2007 delivers command lines to clients and can force those command lines to run with administrative rights using the Local System account. Configuration Manager 2007 command lines can be batch files, scripts, Windows Installer files with .msi extensions, executable files – any file that the operating system can run, Configuration Manager 2007 can distribute. However, Configuration Manager 2007 does not actually package any software for distribution.

Step by Step SCUP installation and configuration with SCCM

SCUP ( System Center Update Publisher ) is a small utility which can be used to update or patch non-Microsoft third party applications like Adobe Reader, Flash Player, Java, Dell drivers, HP drivers  etc. SCUP utilize existing SCCM and WSUS as a update engine. I have collected a list of videos from Technet which tells you how to to do “ Step by Step SCUP installation and configuration with SCCM”.

How to migrate SMS 2003 packages to SCCM 2007

I was searching for the options to SMS 2003 packages to SCCM 2007 ang came across an this  article which has a nice info regarding the same .

As per the author following are the option we can consider:

Option A:
1. Build a new SMS server and attach it to the current central server.
2. Packages and collections will get replicated automatically.
3. Detach the server from the existing hierarchy.
4. Upgrade the server to SCCM.

Option B:
There is a tool from Microsoft called “CopySCCMObj” which you can get from your Microsoft TAM. It will help you migrate not only Packages but also Collections and Advertisements. (Technet Thread discussion)

Option C (Kim’s solution):
1.Install SMS 2003 SP2 on new server.
2.Attach new SMS 2003 SP2 site as a child site.
3.Let objects replicate.
4.Break Parent – Child relationship.
5.Upgrade new Site to SCCM 2007 .
6.Install KB945898.
7.Migrate clients to new site.
8.Remove boundaries from original site.
9.Add boundaries to new site.
10.Decommission original site .
11.Migrate non-replicating objects (queries/reports).

Option D :
1. Take the backup of SMS central server.
2. Restore that in LAB environment.
3. Upgrade it to SCCM.
4. Build another SCCM server with the site code and name (which you are planning for new SCCM hierarchy) and attach it to the central server.
5. All the packages and collections will get replicated.
6. Take the backup of the later SCCM server and restore it in production environment.