Windows Sever 2012 roles and features migration guide

Microsoft has published documents and tools on the TechNet to guide us through the migration of roles and features to Windows Server 2012.

http://technet.microsoft.com/en-us/library/jj134039.aspx

 

The trust relationship between this workstation and the primary domain failed

At times, domain computer might lost it's trust relationship with the domain controllers.  What it means is that the secure channel between the domain computer and the domain controller is broken.  It could be due to computer has past the time it requires to reset the password with the domain controller (> 30 days), the local security authority is out of sync with the DC etc.

DO NOT disjoint it from the domain and re-join it back to the domain (before you reset the computer account) as it will get a new SID and loose all the group membership.

You should do one of this:  (Off course, my preference is No.3)

1. Use Active Directory Users and Computer, Reset the computer account.  Logon to the computer and rejoin it back to the domain.

2.  Use DSMOD computer "cn=win7-1,ou=......" -reset.  Logon to the computer and rejoin it back to the domain.

3.  On the computer:   nltest /server:win7client /sc_reset:domain\dc01   (The server: actually meant the workstation...  No reboot or rejoin)

4.  On the computer, powershell : Test-ComputerSecureChannel -repair

Recovering SRV records from DNS

If you happen to find that the SRV records are gone in your DNS for whatever reason, the quick and easy way to restore the SRV records are from the following command:

nltest.exe /dsregdns

Please note:

netdiag.exe /fix is deprecated and should not be used

dcdiag.exe /fix does not fix your SRV records.

Working with Windows Server 2012 Server Core

Some of my notes for working with Windows Server Core.

To enable Remote Desktop Connection on Windows Server 2012 Server Core
- Navigate to c:\windows\system32
- cscript.exe scregedit.wsf /AR /v
- If the fDenyTSConnection is "1" then RDP is not allowed.
- Run the following command and change the value to zero
- cscript.exe scregedit.wsf /AR 0

To enable GUI on Server Core
- powershell
- Import-module ServerManager
- Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart

To change from full GUI to minimal GUI
- Go to Manage
- Remove Roles and Features
- Select local server
- Skip the role section and next
- Leave the "Graphical Management Tools and Infrastructure"
Powershell : Uninstall-WindowsFeature Server-Gui-Shell -whatif

To change from server core to minimal UI
- install-WindowsFeature server-Gui-Shell

Configuring Server Core
- PowerShell  (-computername < >)
- Other command and alias (cmd, dsim, netsh...)
- Remote Admin
- Sconfig (cool)

Setting network configuration
- netsh interface ipv4  show interfaces
- netsh interface ipv4 set address name="ethernet" source=static address=192.168.1.20 mask=255.255.255.0 gateway=192.168.1.254
- netsh int ipv4 add dnsserver name=ethernet address=192.168.1.2 index=1

Setting computer name, join the computer to the domain and add user
- netdom renamecomputer %computername% /newname:Win2012Core /userd:administrator /passwordd /reboot:0  (To rename the computer name)
- netdom join %computername% /domain:crf.com /userd:administrator /passwordd: /reboot:5  (to join the computer to the domain)
- net user JaneUser /add *  (to add a user)
- net localgroup Administrators /add JaneUser

Use SConfig to do the configurations

Making changes to firewall
- netsh advfirewall firewall set rule group="remote administration" new enable yes
- netsh advfirewall set allprofiles state off
- netsh advfirewall reset


Installing Directory Services
- Install-WindowsFeature -name AD-Domain-Services
- Install-ADDSForest -domainname "abc.com"
http://technet.microsoft.com/en-us/library/hh472162.aspx#BKMK_PS

Publishing and Content Deployment with SharePoint 2010

There are a lot of build-in nice features with SharePoint 2010.  One of the them which I love most is the ability to author content, get approval and publish the content from a staging farm to publishing site.

Denis Stadler has an excellent post here which I am not going to repeat.  Kudos to the trainer.

http://www.denisstadler.com/sharepoint-2010/sharepoint-2010-publishing-feature/a-simple-web-content-management-how-to-authoring-approval-publishing/

SharePoint 2010 Farms Configuration and Concepts Notes.

Sharepoint 2010 Farm Configuration  - My Notes!

- Application Management |  Manage Web Application and take note of the existing web application, such as Central Administrations.
- In Central Administration on the left | Configuration Wizards | Farm Configuration and launch the Farm Configuration Wizard
- Start the wizard, use an existing account "sp_admin" for the time being and select the services that need to be activated.
- Provide a name to the Title for the first site colletion, team site and OK and Finish.
- In the Manage Web Application, you will see the new sharepoint - 80 site and in IIS y ou will see the Sharepoint - 80 site.
- In the Service Application | Manage Application Services. you will see other services started.


SharePoint Concepts:
- Most work are done in Central Administration and powershell
- Within Central Administration, you can create web application and site collections and you can configure your service application.

So, what is web application?
Web application is an IIS site that will contain SharePoint site collections.  (IIS virtual servers)  It might contain one SharePoint site collection or it may contain multiple site collections
It has it's own application pools and can be restarted independently in IIS.
A web application is created when we run the SharePoint farm Configuration Wizard and a site collection is created as well.

What is Service Application?
- Service application is a term to describe the model of share service in SharePoint 2010.
- SharePoint 2007 had an application model called Shared Service Provider (SSP) which has limitation.
- With SSP, services are all combined.
- In SharePoint 2010, service application are running unboxed and independently.
- Service application runs independently of each other and in some cases can be shared between SharePoint farm.
- Service Application available:
Access Services
Application Registry Service
Business Data Connectivity Service
Excel Services Application
Lotus Note Connector
Managed Metadata Service
PerformancePoint Service Application
Search Service Application
Secure Store Service
State Service
Usage and Health data collection
User Profile Service Application
Visio Graphics Service
Web Analystics Service Application
Word Automation Services etc.

- For each of these service application,  there is an Application Connection (Proxy) - creates the connection point for the application.  Connection point for service application and web application

- Application Connection Group (Proxy Group):  Logical grouping of application connection.


Managed Accounts Overview
Service Accounts:  User accounts that are used by services to work with and log into Windows.
- Challenge is having a password change policy with service account due to the manual intervention necessary to adjust password on these services
- Typical the policy is ignored for services account.

SharePoint 2010 has the ability to
- Configure permission for any identity assigned to a service application
- Change passwords for managed accounts in AD and for SharePoint

Go into Security |  General Security | Configure managed account
You will the registered managed accounts.  You can click on the Edit icon to see all the information and options about that account.

Upgrade MOSS 2007 to Sharepoint 2010... My Notes!

Upgrade MOSS 2007 to SharePoint 2010...  My Notes!

Things to consider before the upgrade
OS architecture?
SharePoint services 3.0?
Using 32 bit of SQL on Windows Server 2003?
Upgrade path?

Methods:
- In-place upgrade
- Database attached
- Hybrid (combination of both)

In-Place Upgrade
- If server OS and SQL version is up to date, e.g. 64 bit etc.
- Take MOSS offline during the process.
- Easiest solution but need to allow for down time.

Database Attached  (more like a migration)
- More like a migration.
- Moving the content of the existing server and moving it to a new server and a new server farm.
- Moving it to a new hardware and everything should  be compliant, start from scratch
- The negative side is that there is a bit of more.
- No server down time.  Bring all the data over but not the configuration.
- After the migration, there is a bit of a clean up to do.

Hybrid
- Make existing "Read Only" while working on the contents on the new server
- In-place to upgrade the farm and settings and then detached and upgrade multiple database in parallel on the same farm or a separate farm.
- Preserve farm wide settings
- Upgrade multiple database at the same time.
- More planning.


Perform pre-upgrade check
- At least MOSS 2007 Sp2
-stsadm -o preupgradecheck  (program files\common files\microsoft shared\web server extension\12\bin)
- note that stsadm has been deprecated by powershell command
- The report will show support upgrade types.

In-Place Upgrade:
- Make sure we have a backup and perform a recovery to ensure the back works in the event that the upgrade failed.
- Install the prerequites.
- Kick off the installation
- Installation will detect an installation of SharePoint and will offer the "Upgrade earlier versions"
- Launch product configuration wizard.
- Visual upgrade dialog, you change or preserve the look.  E.g.  Ribbon.  (One way ticket, can only be reversed using powershell)
- Preserved the visual for the time being and let admin decided when the upgrade the visual
- Finish installation and Central Administration will start for monitoring the upgrade.

You can initial the visual upgrade by:
Powershell (for site administrator) to imitate a site collection upgrade.
or
Handle page by page or site collection visual upgrade.
- Go to Site Actions | Visual Upgrade, it will bring you to the Site Settings | Title, Description, and Icon
- You can select "Preview" to have a look at the visual.
- Go to Site Actions | Site Settings | Site Collection Administration | Visual Upgrade.  You can hide Visual Upgrade or Update All Sites.

After In-place upgrade:
- Fixing the photo store
- Some user profile property changes
- perform a full search crawl to rebuild the search index.

Database Attached Upgrade
Backing up the database on the SQL side and moving it to the new SharePoint 2010 server to reconnect to the new site collection.  This method not often perfect as there maybe warning messages about pieces that are missing or services aren't exact, you can go back and ensure services are install.  Create a brand new install of SharePoint 2010 with temporarily SharePoint farm with team site collection.

- Decide if you want to allow the content database to continue service or set it as "read only"
- Detach the content database
- Copy to the 2010 server
- Attach to the new farm

Steps (roughly):
On the existing MOSS 2007 server:
- Open MOSS SharePoint Site Central Administration | Application Management on the left, under SharePoint Web Application Management, go to Content Database.  It will show the database name.  Select different web application from the drop down list to see other database.  (WSS_Content_XXXX)
- Open SQL Management Studio, select the WSS_Content database, go to properties | options and scroll down to select "true" for database read-only.
- Select the WSS_Content database, right lick and go to task and backup...  specify the destination and give it a useful name.. MOSS2007_content or something.  Specify a useful destination path.
- Locate the backup file and move it to the SharePoint 2010 server

On the SharePoint 2010 server:
- Start SQL Management Studio
- Right click Databases on the expanded tree and restore database.
- Provide a new database name such as "moss2007" and "from device" (select the backup file) and select the database, click OK and restore.
- Now you want to go to your temporary site which you have created on the SP2010, disconnect the existing database and reconnect to the new database.
- Go to Central Administration, Application Management on the left, Databases (Manage content database).  Select WSS_Content (for the standard top level site), scroll down, tick the "remove content database"  (we are not removing the database, just removing the connection to the site..).  You will get a warning and OK.

- Open SharePoint 2010 Management Shell (powershell)
- test-spcontentdatabase - name moss2007 -webapplication http://sp2010 [enter]
- As long as we don't see any upgrade block set to true then we should be fine.
- mount-spcontentdatabase -name moss2007 - databaseserver sp2010 -webapplication http://sp2010 [enter]
- In Central Administration, you will see that the Web Application the moss2007 pointing to http://sp2010 and if you go to the main site, the migrated content database will be online.
- Something might not came through such as the picture etc.  Move the pictures over to _layout folder.  Discover where the path is from IIS,  E.g.  Go to SharePoint - 80 and go to _layouts.  Right click and go Explore.
- Go to Site Action and Visual Upgrade and upgrade to the new visual.

Installing Sharepoint 2010.. My Notes

My notes on installing SharePoint Server 2010.

User Accounts Requirement:
"Least privileged" is idea of assigning only what is needed for the account to function.

1.  sp_admin - Sharepoint Setup User Account.(member of the local admin)
2.  sp_sql - SQL Server Service Account.  (no administrator privilege on the OS)
3.  sp_farm - Server / Farm Database Access Account.

SQL Installation
SQL Server 2008 R2
- SQL Server Feature Install
- Database Engine Services and Management Tools
- Keep default instance
- SQL Agent (sp_sql account)
- SQL Database Engine (sp_sql account) - Complete.
- Windows Authentication Mode
- Specify SQL Server Administrator - Add current user
- Complete the install.

In Microsoft SQL Server Management Studio
- Connect
- Goto Security | Login
- Right click and new login
- Create domain\sp_admin and in Server Role, enable dbcreator, securityadmin.

In Local Users and Group
- Add domain\sp_admin into local administrators group.

Login to sp_admin into the SHAREPOINT server
- Run the setup.hta and complete the "Install software prerequisites".
- Install Sharepoint server
- Insert product key
- Accept the terms
- Select server farm
- Select complete install.  (standard alone installation is the same as the previous standalone version).
- When finish, close and Sharepoint Products Configuration Wizard will begin
- Next and yes to restart the services/reset
- Create a new server farm
- Name of database server
- Database name would be default Sharepoint_Config
- Database Access Account, Username sp_farm and insert the password
- Might receive error about not able to connect database master sql server and no permission.
- Make sure SQL server firewall is allowing traffic in, otherwise create inbound rules. 1433
- Specify the passphrase  (very import to take note that in order to join to this server farm, you need to know the passphrase)  Complex rule applies
- Specify the port number:  e.g.  12345
- Select  NTLM for easy working sharepoint site, however, kerberos is recommended.
- Summary is provided and click yes to kick off the configuration.
- Exit the installation if successful.

Configure your sharepoint site.
- Select the wizard or do it yourself.  Select the wizard at this stage.
- Best practice is to create a new managed service account.
- Create a service account call something like sp_service in the domain
- Provide the domain\sp_service account info into the field.
- Check through the services which are enable by default.
- Services will affect the performance of the server.  De-select those that are not needed.
- Once completed, you will be given the the option to create you new first site.
- Insert a title and description.
- In the Web Site Address.  You don't have to put in the URL.  leave it as default
- Select the template.  Select team site.  (for starting..)
- OK and complete the farm configuration wizard.
- Click on the link and open in new tab to show your team site
- Click finish to bring up the central administration site.
- Add to local Trusted Sites.


Sharepoint farm and advanced deployment.
Components:
Web server
Application server
Database server

Single Tier
All 3 components in one server

Multi-server 2 Tier Deployment
Web and Application on one server
Database on one server

Multi-server 3 Tier Deployment
Web, Application and Database on individual server

High availability
Failover Clustering on SQL server.
Network Load Balancing on the Sharepoint site. (Web Frontend)

Note:
- When there is a problem with the installation, check the installation log files in %temp%
- Installation can be scripted. setup /config config.xml
- Language packs can be downloaded from Microsoft to support multilanguage site.

Deployment of PKI Certificates Required for Configuration Manager Native Mode

This post is about my experience with configuring Microsoft PKI to provision certificates requirement for Configuration Manager to run in native mode.  Please note that I am working with Windows 2008 Certificate Authority and SCCM 2007.

A lot of the stuff here are duplicated and copied from these TechNet Articles.

Step-by-Step Example Deployment of the PKI Certificates Required for Configuration Manager Native Mode:  Windows Server 2008 Certificate Authority. 
http://technet.microsoft.com/en-us/library/cc872789

Deploying the PKI Certificates Required for Native Mode.
http://technet.microsoft.com/en-us/library/bb680312

Windows Server 2008 Active Directory Certificate Services.
http://technet.microsoft.com/en-us/windowsserver/dd448615.aspx

Active Directory Certificate Services Step by Step Guide.  http://technet.microsoft.com/library/cc772393(v=ws.10).aspx

PKI certificates must be installed prior to configuring Configuration Manager 2007 to operate in native mode.  The follow describes 3 types of PKI certificates that are required and describes how they are used in Configuration Manager 2007 native mode.

Three types of PKI certificates
Site server signing certificate - This certificate is install on the Configuration Manager site server.  It is used to sign client policies.

Web server certificate - This certificate is installed on servers that will be Configuration Manager 2007 site systems, with roles such as the management point and distribution point. It is used to encrypt data and authenticate the server to clients.

Client certificates - This certificate is installed on computers that will be Configuration Manager 2007 clients, and it is installed on the management point. It is used to authenticate the client to site systems; on the management point it is used to monitor the server's operational status.

The site server will require the signing certificate.  The management point, software update point, distribution point and the state migration point (web server) will require the web server certificate.  Lastly, the Configuration Manager Client will require the client certificate and the management point will also require the client certificate to report its status to the site server.

I followed these steps to provision all the certificates.
http://technet.microsoft.com/en-us/library/cc872789#BKMK_siteserver12008

Once the PKI certificates are provisioned, follow the Administrator Checklist: Migrating a Site to Native Mode.  http://technet.microsoft.com/en-us/library/bb632727

Issues I have encountered:
Software Update Point reported errors trying to communicate with WSUS.  This is due to the WSUS installed on a separate website on port 8530 and 8531 HTTPS rather than the default website.  Enabling the certificate on the WSUS intranet fixes the problem.

Install printer drivers without being a local administrator.

To enable a normal user to be able to point to a network printer, install the drivers and print.  the follow will need to be in place.

1.  Enable the following group policies:  Computer Configuration | Administrative Templates | System | Driver Installation | Allow non-administrators to install drivers for these devices setup classes.

2.  Printer Classes GUID would be :  {4d36e979-e325-11ce-bfc1-08002be10318}
 A list of classes can be found here.

3.  Computer Configuration | Administrative Templates | Printers | Point and Print Restriction.  Disable this setting.

When the policy setting is disabled: 
-Windows Vista client computers can create a printer connection to any server using Point and Print.
-Windows Vista computers will not show a warning or an elevated command prompt when users create a printer connection to any server using Point and Print.
-Windows Vista computers will not show a warning or an elevated command prompt when an existing printer connection driver needs to be updated.


Reference:  http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/df21d2c2-c2d4-4107-bfe3-bf8c5a1cd946/

Microsoft ForeFront Endpoint Protection 2010

Prerequisites
http://technet.microsoft.com/en-ca/library/ff823830.aspx

You might get an error about Setup cannot verify the service principal name (SPN) for this account
- Elevate a command prompt and execute the following command.
setspn -A MSSQLSvc/<SQL Server Name>:1433 <domain>\<user>    <--SQL Service Account

Download Microsoft Forefront Endpoint Protection (FEP) 2010 Update Rolloup 1 Tools:
http://www.microsoft.com/download/en/details.aspx?id=26613

How to use the Definition Update Automation Tool for Forefront Endpoint Protection 2010 Update Rollup 1.
http://blogs.technet.com/b/clientsecurity/archive/2011/11/03/how-to-use-the-definition-update-automation-tool-for-forefront-endpoint-protection-2010-update-rollup-1.aspx

I personally like the "Status Filtering Rules Method" as it monitors the statemsg and as soon as the Wsus Sync Manager finished synchornising with Microsoft, it will kick off the batch file to update your deployment package and assignment.. 

Performing and Active Directory Health Check

There are a few Microsoft diagnostic tool you can run to do basic Active Directory health check.

dcdiag.exe is an utility that will run diagnostic tests against domain controllers. Here is a very good article Ned which I am not going to repeat here. This Technet article documented how this tool can be used with all the switches and results.

dcdiag.exe /v
dcdiag.exe /test:topology
dcdiag.exe /test:replications

The Microsoft I.T Environment Health Scanner is really good.  It has some A.D component in there as well and does all the jobs for you.
http://www.microsoft.com/download/en/details.aspx?id=10116

PD TechGuru Reference:
https://pdtechguru.wordpress.com/2012/10/04/active-directory-health-check/


DNS
DNS is a very important role in Active Directory and should be check first, if DNS is not working properly, you will most likely would have A.D. issues.
http://technet.microsoft.com/en-us/library/cc755349(WS.10).aspx

Some tools that is useful when troubleshooting DNS server issues:
1. DNSLint - http://support.microsoft.com/kb/321045
DNSlint /ad domain_controller_ip /s dns_server_ip

2. DNSCMD.EXE
/info will give you basic information about the DNS.
/zoneinfo <zone_name> display information about the zone.

A.D Replication
The following tools are useful for finding out replication status with A.D.

1. Repadmin.exe admin tool. http://technet.microsoft.com/en-us/library/cc755360(WS.10).aspx
/showrepl
/replsummary


2. dsastat -s:domaincontroller1;domaincontroller2This utility is useful in verifying replication between DCs to ensure that objects been completely replicated throughout the domain.

3. Replmon.exe GUI interface

Good to know:
To determine the FSMO Role.
- Netdom -query fsmo (list the current DC which holes the FSMO roles)
- dsquery server -hasfsmo schema/name/infr/rid/pdc
- dcdiag /test:knowsofrolesholders /v (including test as well..)

To Transfer or Seize FSMO Role.
Use ntdsutil to transfer the role
- Type roles
- connections
- connect to server <domain_controller> where the dc is where you want to transfer to
- quit
- transfer schema master
- quit

User ntdsutil to seize the role if you have lost the original DC for the role.
- follow the steps above but instead of transfer, you specify seize schema master for example.
- One the role is seize, do not attempt to bring the previous role owner up, it will cause the database to be corrupted.

Enable Netlogon logging.
- http://support.microsoft.com/kb/109626
- nltest /dbflag:0x2080ffff

Troubleshooting Replication issues:
http://technet.microsoft.com/en-us/library/cc755349(WS.10).aspx#BKMK_2

Setting up System Center Configuration Manager 2007 ... Revisit...

I have setup a few SCCM sites now and didn't really get a chance to document the steps required to complete a successful setup and also things that require attention.  Most of them have already been documented in TechNet and other sites but for the record, I am going to post some links here.

Preparing Windows Server 2008 R2
- It is important to make sure that you have a good build of the OS and that you have all the updates installed.
- IIS is required on SCCM site system.  Make sure you add the Web server IIS role.
- For Windows Server 2008 R2, additional configuration required.  http://technet.microsoft.com/en-us/library/cc431377.aspx

SCCM 2007 Prerequisites
- Prerequisites information on TechNet http://technet.microsoft.com/en-us/library/bb694113.aspx
- Extending the schema.  (Recommended) and create the System Container and apply the right permission.  http://technet.microsoft.com/en-us/library/bb633121.aspx
- Create a sccm server active directory group and grant sufficient access to the system management container.
- Install the features and modify the WebDAV settings as per article.
- At times, you will encounter weird issues with WebDAV as detail in this article.  Correct the problem as specify. http://www.ithastobecool.com/2009/06/24/sccm-2007-r2-on-server-2008-weird-webdav-errors-on-mp-installation/
- Install WSUS  (3.0 SP2)


SCCM2007 Central Site Installation
- Run the setup and prerequisites checker.
- Prerequisites checks rule descriptions can be found here.  http://technet.microsoft.com/en-us/library/bb680951.aspx
- Check if the site information is being published to the Active Directory Domain Services if the schema is extended.  http://technet.microsoft.com/en-us/library/bb693614.aspx
- Create a sccm_servers active directory group and grant sufficient access to the system management container.


How to verify successful site installation.
http://technet.microsoft.com/en-us/library/bb693526.aspx


Installing SCCM 2007 R3.
- Install hotfix KB977384 as it is required before R3 can be installed.

Deploying to multiple sites.
http://technet.microsoft.com/en-us/library/bb693675.aspx

How to install a secondary site.
http://technet.microsoft.com/en-us/library/bb632837.aspx

- For Windows Server 2008 and 2008 R2. http://technet.microsoft.com/en-us/library/cc431377.aspx
- Including WebDAV, enabling and configuring WebDAV
- Set RequestFiltering Rules
- Ensure that the secondary site server has sufficient access to the the System Management container in the schema.

Prerequsites for Software Distribution.http://technet.microsoft.com/en-us/library/bb680335.aspx


Branch Distribution Point
http://technet.microsoft.com/en-us/library/bb680335.aspx



About site to site connection group for multiple hierarchy setup.
http://technet.microsoft.com/en-us/library/bb632850.aspx

Troubleshooting Client Push issues.
http://support.microsoft.com/kb/925282

Windows 7 Deployment with SCCM OSD (Reference)

I came across a lot of articles about building Windows 7 with SCCM OSD.    Here are a few good ones... and I think the authors have done an excellent work documenting them and sharing those knowledge.

Building Windows 7 with SCCM OSD Step by step
http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/

http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx


Customizing Windows 7 deployment Part 1 - How can I change the regional, keyboard, locale etc in Windows 7
http://www.windows-noob.com/forums/index.php?/topic/1660-customising-windows-7-deployments-art-1/

Customizing Windows 7 deployment Part 2 - Creating collection variable
http://www.windows-noob.com/forums/index.php?/topic/1685-customising-windows-7-deployments-part-2/

Customizing Windows 7 deployment Part 3 - Power management settings
http://www.windows-noob.com/forums/index.php?/topic/2283-customising-windows-7-deployments-part-3/

Customizing Windows 7 deployment Part 4 - Language Pack
http://www.windows-noob.com/forums/index.php?/topic/3251-customising-windows-7-deployments-part-4/

Customizing Windows 7 deployment Part 5 - Getting Bitlocker to work
http://www.windows-noob.com/forums/index.php?/topic/3875-customising-windows-7-deployments-part-5/

Setting computer name during deployment.
http://www.windows-noob.com/forums/index.php?/topic/3875-customising-windows-7-deployments-part-5/
http://osdeploy.wordpress.com/2008/08/05/easy-way-to-change-pc-name-during-deployment/
http://t3chn1ck.wordpress.com/2009/04/24/script-to-prompt-for-system-name-in-sccm-osd/

Basic troubleshooting guide and location of the log files.
http://hayesjupe.wordpress.com/sccm-osd-basic-troubleshooting/

Troubleshooting the PXE point and WDS in Windows 7
http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx