How To
This category contains instructional and education information pertaining to technology.
Windows 7 is coming
With Windows 7 public availability around the corner, ADNS will be making the move this Friday. We will report our experiences on this blog with all aspects from upgrades (Vista only) and new installations.
Majority of our workstations are Dell Vostro 400s, so we should not have any issues meeting the recommended system requirements.
Here are some specs to help get you ready:
Minimum requirements-
- 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
- 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
- 16 gigabyte available hard disk space (32-bit) or 20 GB (64-bit)
- DirectX 9 graphics device with WDDM 1.0 or higher driver
Check back Friday 8/7 for part 1: Installation.
SharePoint and Mapped Drives…
An incredibly useful feature of SharePoint Document libraries is their ability to use the WebDAV protocol to be accessed via Windows Explorer.
The below scenarios will use screen shots and steps from a Windows XP Pro SP3 workstation that is NOT bound to the same domain as the SharePoint Implementation. This mimics behavior that would be seen by a kiosk or dedicated printing workstation. The SharePoint installation is based on SharePoint Services 3.0 SP2, running on Windows Server 2003 (IIS 6) with WebDAV extensions allowed.
Log in already!
One of the biggest user peeves with SharePoint is the authentication prompts. I get questions about this all the time, so I thought I would explain some simple configuration changes either you or your system administrator can implement to make your SharePoint experience just a bit better.
There are 2 scenarios that I will cover:
- Visiting the site from your work network; this assumes your workstation is bound to the same domain as the SharePoint implementation.
- Visiting a SharePoint site of another company, such as an extranet for a partner company. This would assume your workstation is bound to a different domain than the SharePoint implementation –or- Visiting the site from a workstation that is not bound to any domain (home computer or workgroup).
There are of course scenarios where you will get prompted regardless, in case 2 above, if you open a Microsoft Office document (Excel, Word, etc), after the corresponding Office application opens, you will be presented with a dialogue box requesting your credentials. This is by design, meaning when the Office application opens, it is initiating a new session to the server, this new session does not have access to the credentials you offered up when initially logging into the site.
If you fall into the category of case 1, and you are being prompted for credentials when opening Office documents from SharePoint libraries, follow the procedure described for that scenario.
3-party IM conference with OCS 2007 and OCS 2007 R2
OK, so you just got your shiny new Office Communications Server (OCS) 2007 (R1 or R2) implementation up and running, and whoa!, you start receiving complaints that users are unable to initiate multiparty instant messaging (IM) sessions, or multi-party conferences.
The setup:
OCS 2007 R1 and R2 (Standard)
Cisco Unified Presence Server v7.0.2
Cisco Call Manager v7.0.1.11000-2
In OCS 2007, the error reads as:
“Your attempt to start a conference was unsuccessful. If you need further assistance, contact your system administrator.”
Love for the Linux Users
It never hurts to have a quick reference for Linux administration commands, so I wanted to put out some helpful items for user, file, directory, and group management.
Move all databases (Office SharePoint Server 2007)
If you’re like me, this is definitely in your Top 10 WSS/MOSS 2007 requests.
Never fails, the database server is provisioned with less than adequate storage, or the company utilization and adoption of SharePoint has been more than successful.
None the less, the SharePoint and related databases have or are on track to outgrow their environment. This used to be a trial and error procedure, as there was no clear documentation from Microsoft, and community documentation was, less than complete.