My IT Resource Book

Monday, September 9, 2013

Server 2008: Rename Your Active Directory Domain

Server 2008: Rename Your Active Directory NetBios Name

Recently began setting up my own personal production and test networks on my personal VM host (VMware Esxi 5.1). I had purchased a domain from GoDaddy and planed on using "internal.domain.com".

Shortly after setting up the first Domain Controller realized I need to change my NetBois to allow login as domain\user instead of internal\user.

Some quick Google searching provided the following resource:
http://www.trainsignal.com/blog/rename-active-directory-domain

Step 1: Access Domain Controller

Step 2: Open a command prompt

Start > Run > cmd

Step 3: Generate Domainlist.xml

From command prompt enter "rendom /list"

2008R2 directory: C:\users\[logged in user]

Step 4: View list.xml file

From command prompt enter "type domainlist.xml"

Step 5: Edit Domainlist to correct NetBios name

Browse to file location

2008R2 directory: C:\users\[logged in user]

Right-click and select edit (use favorite text editor if prompted)
Locate
Change NetBiosName value from current (internal) to desired (domain)

Note I only wanted to change login from internal\user to domain\user if you wish to change domain completely update all instances of old value to new desired value.

Step 6: Verify desired changes

From command prompt enter "rendom /showforest"
Verify results

For domain login ensure FlatName is what you want
For entire rename ensure correct values for all fields

Step 7: Upload changes

From command prompt enter "rendom /upload"

Step 8: Prepare domain controller for update

From command prompt enter "rendom /prepare"

Best practice is to ensure all domain controllers have firewall off for remainder of operation

Step 9: Execute domain update

From command prompt enter "rendom /execute"

Verify no errors on results if so resolve before continuing (issue I ran into was firewall issues)
Note Domain Controllers may begin restarting.

(Al-Dabbas stated his did, my experience they did not)

At this point I was able to logoff then back on as domain\user with now issues. As I had just created the domain I did not need to continue past Step 6 of TrainSignal Blog their remaining steps walk you through updating any previous GPOs that were created.

Monday, September 2, 2013

SharePoint 2010: Hide Recently Modified

For our internal SharePoint each of our departments have a page. Since we are using the Team Site template the pages are Wikis. As this does not look professional I had to find a way to block on several pages (10-12 pages).

I did some searching and found you could do this two ways.

First way is per page and requires the Content Manager, following site provided the directions below: http://blog.drisgill.com/2010/09/sp2010-branding-tip-12-hiding-quick.html
This process works good for a few sites (1-3).

Navigate to desired site
Click Page > Site Actions > Edit Page
Click Insert > Web Part
Under Media and Content > Content Editor > Add
Select the new webpart
From ribbon click Format Text > HTML > Edit HTML Source
Enter the following and Click Ok:

8. Hiding the Content Editor

Webpart Tools Options > Web Part Properties
Expand Appearance
Modify Chrome Type to None
Click OK
Save and Close page

Second way is to modify the site collections master page. Following site provided directions:

http://howididit-sharepoint.blogspot.com/2012/06/sharepoint-2010-hide-recetly-modified.html

Navigate to Site with pages
Click Page > Site Actions > Edit in SharePoint Designer
Select Master Pages from Site Objects
Select your master page to edit

Default is v4.master

Click Edit file

Check out if prompted

In code window scroll up till in the <head></head> section
Enter following code somewhere between the <head></head> tags

<style type="text/css">.s4-recentchanges{display:none;}</style>

Save the file
Navigate back to Master pages
Right click on page just edited and select Check In

Select Publish a major version
If prompted for content approval click yes

Browser will open

Select file Pending Approval
From drop down click Approve/Reject
Select approved and add comments if desired, click OK

Until approved changes will not take affect

Refresh the page and verify changes applied.

Monday, August 26, 2013

Spiceworks: Generate Ticket for upgrade notice

This is quick write up of experience implementing How-To: How to automatically create a ticket on Spiceworks upgrade by Vasily Ignatov.

Objective: Generate a ticket in Spiceworks when upgrade is released. Provides upgrade history and ensures completed in timely manner.

Navigated to following link and save the script:

http://community.spiceworks.com/scripts/show/2077-auto-ticket-on-spiceworks-upgrade

Create a storage directory

Create a directory for downloaded Spiceworks installers and define the path_to_store_exe variable in the script. Grant write access to this folder for account, which will run the script.
We used \\server\shared\IT\Software\Spiceworks\Installers

Fill in other variables in the script

All settings to fill in bounded with lines "=== Define your parameters ==="

$smtp_server = "smtp.domain.com"
$smtp_server_port = "25"
$SSL_is_used = $false
$ticket_creator_email = "admin@domain.com"
$ticket_creator_email_pass = ""
$helpdesk_email = "helpdesk@domain.com"
$helpdesk_url = "http://helpdesk.domain.com:port"
$path_to_store_exe = "D:\SW-Install\"
$LANG = "EN"

Schedule a task Schedule a task to run the script every day at 09 AM or whenever you want.

Start > Run > Taskschd.msc
Task Scheduler Library > Action > Create Task
General

Name: Spiceworks Ticket Upgrade
Description: Run PS script to check for Spiceworks updates. Generate ticket as needed.
Security Options: Run whether user is logged in or not

Triggers

New > On a schedule
Settings

Define when you want to run

Advanced Settings

Ensure Enabled is checked
I like to set stop for tasks if they run more then an hr

Actions

New > Start a program
Settings:

Program/script: powershell
Add Arguments: -file [path to script enclose in "" if spaces in path]

Conditions

Adjust as needed

Settings

Adjust as needed

History

Log to verify running

Upon saving will be prompted for user password

That is it. Now in the folder you have defined installers will be downloaded being named according to versions. Also in the folder will be the log file (check_sw_ver.log) and the md5sums.

Download script, readme and task scheduler template at:
https://docs.google.com/file/d/0B1fwreWrAZiobmlXT1Y1ZGpCSEE/edit?usp=sharing

Friday, August 23, 2013

SharePoint 2010: Create new Site Collection

Quick run through on how to create a Site Collection on SharePoint 2010 for future reference.

For more details check out:

SharePoint 2010 Server: http://technet.microsoft.com/en-us/library/cc263094(v=office.14).aspx
SharePoint 2010 Foundation: http://technet.microsoft.com/en-us/library/cc263165(v=office.14).aspx

Access Central Administration site

Typically server name on port 9999 but will vary with installation. On server shortcut located at: Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration

Application Management > Create site collections
Complete following:

Web Application

Select Web Application from drop down
Ex: Test

Title and Description

Title: What you want displayed above Ribbon
Description: Describe the site for future reference

**DO NOT LEAVE BLANK** future admins will HATE you

Web Site Address

Select if Root (/) or Sites (/sites/) address

Template Selection

Select desired Template:

Good sources for template definitions:

Primary Site Collection Administrator

Enter User Name:

I define Farm Admin as primary

Secondary Site Collection Administrator

Enter User Name

Define my privileged account as secondary
Can add more SC admins later if needed

Quota Template

Define quota if required

Click OK; Wait for processing

Completed screen provides hyperlink to new site collection

Check out the How-To on Spiceworks:

http://community.spiceworks.com/how_to/show/47536-sharepoint-2010-create-new-site-collection

Wednesday, August 21, 2013

SharePoint 2010: Creating New Web Application

Little write up on process of creating Web Applications for future referencing on later posts, avoid having to duplicate data over and over.

I will not be explaining all the options for those details check out:

SharePoint 2010 Server: http://technet.microsoft.com/en-us/library/cc261875(v=office.14).aspx
SharePoint 2010 Foundation: http://technet.microsoft.com/en-us/library/cc288705(v=office.14).aspx

Access Central Administration site

Typically server name on port 9999 but will vary with installation. On server shortcut located at: Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration

Application Management > Manage web applications
Click New
Complete following:

Authentication

Classic Mode Authentication

IIS Web Site

Create a new IIS web site: SharePoint - Test

Scheme I use is SharePoint - [SiteSubject]

SharePoint - HR / SharePoint - My Sites / etc

Port: Typically 80 unless known issues
Host Header: what you want the URL to be

http://[hostheader]:port

Path: Leave as defualt

Security Configuration

Leave all as default unless you know you are using Kerberos/SSL or want to allow Anonymous (Public Sites)

Public URL

URL: Leave default unless want different from Host Header
Zone: Can't change

Application Pool

Create new: I just double check to make sure scheme is being applied: SharePoint - [hostheader][port]
Security Account: Leave as defualt (Typically Farm Account)

Database Name and Authentication

Database server: [Enter Database Server DNS Name]
Database Name: Modify to following scheme

WSS_Content_[IIS Web site Name]

Ex: WSS_Content_Test (makes easier to find in SQL database

Database Authentication: Leave default unless your network requires it

Failover Database Server: Enter Server name if you have mirrored SQL servers
Search Server: Select desired Server if available
Service Application Connections

Leave as default unless new web application does not require Service Application

Customer Experience Improvement Program: No

Click Okay; Wait for processing to complete
Application Created Should Appear

Check out How-To on SpiceWorks:

http://community.spiceworks.com/how_to/show/47537-sharepoint-2010-creating-new-web-application

Monday, August 19, 2013

SharePoint 2010: My Site Root Deletion/Restoration

So playing around in our My Sites and discovered a My Site for SP_Farm. Went in and deleted as a typical site collection. BIG MISTAKE. Apparently when browsing other My Sites you are view a layered root site (/). By deleting this I broke My Sites for everyone. To resolve I had to recreate the Site Collection (followed post at Jerry Orman's Blog SharePoint My Site link stops redirecting users to their Personal Site)

Browse Central Administration > Application Management

Click Create Site Collection
Select the My Site Web Application
Set the Title to My Site
For URL, select the "/" option for the root
Select the My Site Host site template on the Enterprise tab
Set the SharePoint System account as the owner.
Click OK

That fixed it (whew thought I would have to recreate all the My Sites from a backup last week).

If you want to remove those service account My Sites there are two ways (GUI / PS):

GUI (Central Administration)

Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration
Application Management
Delete Site Collection
Select Site from Drop Down
Delete

PS (Power Shell)

Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell
STSAdm.exe command-line (stsadm -o deletesite -url http://mysite/personal/bobsmith)

Check out How-To write up on SpiceWorks:
http://community.spiceworks.com/how_to/show/47509-sharepoint-2010-my-site-root-deletion-restoration

Windchill 10.0 Debug Logging

We have been having some issues with our WindChill/PTC Creo system and have had to reach out to their tech support. Through this issue I have learned how to enable debug logging and what log files they typically need to resolve cases. By knowing this information you can speed up the resolution process by including debug logs with initial case opening message instead of waiting for the tech to request.

Access server running Windchill
Start > All Programs > Windchill_10.0 > Windchill Shell
Enter: xconfmanager -s wt.inf.team.verbose=true -t codebase/wt.properties –p

Set to false to disable

Now reproduce what ever caused your error and you will have a nice debug log to send.

The logs location may vary. Ours are located in [Drive]:\PTC\Winchill_10.0\Windchill\logs