I vaguely remember that work Paul – but I’m amazed you’ve got all those figures
in your head still!
I think Sezai might be able to attest to any general issues using a well set up
SQL/SharePoint/SAN infrastructure. If funds allow, my experience has been that
a well configured vmware
By while it is vmotion do you mean While we are actively moving it
between physical VM hosts ?
If so what did you expect?
If not, we need more details.
VMotion is what lets you reallocate a live running VM in a VMWare
cluster from one physical host to another, while running against their
It would be interesting what Windows server 2008 virtualisation brings to the
table in regards to performance etc...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Brown
Sent: Wednesday, 6 February 2008 7:49 PM
To: listserver@ozMOSS.com
Subject:
I am working with a client at the moment that is writing their own and
just linking to it from Sharepoint. That way when system updates occur
it is transparent to the user. But the gotcha is having to maintain two
separate systems.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Hi There All
Ive been asked to perfrom an in depth documentation process for our single
server moss farm. This should include list of site collections, sites, doc
library's, lists etc etc.
I thought of drawing this up in excel or somtehing but i was wondering if
there was a tool others new of
Hi Greg,
I'm not sure how well they would fit in to what you need, but at first
glance, the Worksheets could provide a solution for you.
I haven't done these myself, however I am looking at doing the, when
currently priorities are finished off.
Link:
Be interested in seeing how this works
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dave Porter
Sent: Thursday, 7 February 2008 12:41 PM
To: listserver@ozmoss.com
Subject: RE: [OzMOSS] Documenting MOSS 2007
You can also use Visio 2007 to import a site and it will build it
Thanks everyone for the replies. The Visio way does sound kinda cool and
should do what i am looking for. Fairly simle to keep up to date i would
have thought as well.
Cheers
Greg
Looks like what he meant is generating a site map. Visio has a site map
generation capability, in which it crawls
Dear All,
I am having a mental blank at the moment and I can't remember for the
life of me how this works.
If I create a custom site definition, create a new site based on that
definition, make changes to the original site definition. Will the
changes be reflected in my sites based on that
Sadly no it won't pick up the changes automatically... but you can force
it to reset to the Site Definition on a per site basis in site settings.
This is MOSS 2007 I'm talking about here of course.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Aaron Saikovski
Sent: Thursday, 7
Depends what changes...changes to aspx pages will affect the existing ones.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hodges, Kristen
Sent: Thursday, 7 February 2008 2:43 PM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] custom site definition question
Sadly no it won't
However I remember with WSS 2.0 you could actually make changes to an existing
Site Def and certain changes would come through to sites already based on those
definitions.
Especially items like new fields that are added at the end of a List definition
or changes to an ASPX page that forms part
Site Definition ONET.xml
Changes to the Site Definitions ONET.XML file won’t be reflected in sites that
have previously been created. Changes will only be reflected only when you
create new sites.
Site Definition .aspx pages modified using notepad or VS.Net
If these pages are modified with
Cool..confirms what i thought
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Hodges, Kristen
Sent: Thursday, 7 February 2008 2:43 PM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] custom site definition question
Sadly no it won't pick up the changes automatically... but
Thats what i thought
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ishai Sagi
Sent: Thursday, 7 February 2008 2:53 PM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] custom site definition question
Depends what changes...changes to aspx pages will affect the existing
ones.
ONET.xml is used for PROVISIONING new sites, but if the site definition
contains .aspx files then these are actually read from the file system every
time (unless customised)
Changes in ONET.xml are read from the XML file the next time you create a site.
So you are stuck if you want your
In your scenario proposed Sezai I might be inclined to instead use Features to
make changes to existing sites and update the site definition with a Feature
reference for new sites created from the site definition.
1/ Create a Feature to add the new functionality to existing sites and deploy.
Reset to site definition resets customised files in the site to the site
definition, but it doesn't 'pick up' ONET.xml changes, which are only read
during provisioning. It resets all customised pages.
Eg.
ONET.xml contains my custom feature -
18 matches
Mail list logo
