as you mentioned yourself moving up your servers to the Top Level Domain will give users from the lower domains access to the portal.
Back up your portals and move the servers to the other domain.
as i can see from what you're stating is that all service accounts etc will still be able to logon...
it is not recommended (even unsupported) to do direct SQLquerys to the database. Use the objectmodel provided....
//Bart
//Bart
http://sharepointblogs.com/bart
sidenote :You don't need SPS to do so: all can be done through WSS also - prefered with isa publishing off course ;-)
addalternatedomain
Note New in Windows SharePoint Services Service Pack 2 (SP2).
Configures the incoming URL and maps it to a URL zone. For each HTTP request, Windows...
It is NOT a document management system, Collaborative Platform is the correct term as you wrote it yourself.
but it can be leveraged as a doc management system, but the product isn't designed for this. It all depends on the requirements the organisation has....
Sometimes Sharepoint works well...
but yes it *should* be possible to replicate in some way (I'm no DBA) but reading through some files it can be done...
CMS on SQL2005 has no real benefits for CMS itself except the speed is fantastic ;-)
//Bart
http://sharepointblogs.com/bart
no special advantages (no new features unlocked or smth ;-)
But SQL2005 rocks ;-), Where we implemented SQL2005 the DB server was also used for some other purposes, CMS and some legacy apps. they seemed to benefit over SQL2000....
//Bart
http://sharepointblogs.com/bart
caching, recycling app pools, metabase stuff all things involved here. This is not abnormal behaviour. I just can't seem to find the info where this proces is described.
//Bart
http://sharepointblogs.com/bart
For more information about the SharePoint Migration Tool (Smigrate.exe), see the "Backup and migration" section of the Microsoft Windows SharePoint Services Administrator's Guide. To obtain the Microsoft Windows SharePoint Services Administrator's Guide, visit the following Microsoft Web site...
use the object model to create sites automatically
and if you want to go further with this idea: there's the runas command which allows your to run stuff under other users context.
Or run you app in an app pool that runs under a domain account with the correct permissions
kind regards
//Bart...
build your own webpage that creates a local user or a domain user. (or have it build for you)
acquire a CAL for every user.
have fun
//Bart
http://sharepointblogs.com/bart
storage is cheap these day's ;-)
but as archiving solution i would recommend Veritas KVS.
but as i said, adding storage is sometimes cheaper ;-)
//Bart
http://sharepointblogs.com/bart
files are stored in the database.
you need to use the object model to to "actions" with these files.
Direct acces to the database is not supported
kind regards
//Bart
http://sharepointblogs.com/bart
this works where size and SLA's permit
if you have some what i call "VIP-sites" and you don't want to invest (yet) in third party products i suggest taking backups with the smigrate utility to separate files (these are the same as frontpage backups)
you will loose security information but for...
if you want a full fidelity backup of your portal environment you should use SPSBACKUP to backup your portal.
(or tools from third party vendors)
SQL backups can be used, but in case of disaster you don't want to wait for rebuilding your indexes etc....
And i hate corrupt indexes ;-)
//Bart...
you might want to read the administrator guide to setup WSS -sharepoint services
once installed and configured this feature in outlook will explain itself....
//Bart
http://sharepointblogs.com/bart
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.