for Sharepoint2k3, updated the
hostheader
in IIS with this new name and then entered it into
the default URL in
central admin under Alternate Access
Properties (or something to that
effect). That eliminated any
clashes.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Greg
clashes.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Greg
Mulholland
Sent: Thursday, 21 February 2008 2:32
PM
To: listserver@ozMOSS.com
Subject: RE:
[OzMOSS]
shrepoint 2003 restore
Hi Guys
Trying to restore a portal from 2003 on a network
Standard or Enterprise?
Regards,
Greg Mulholland
Paragon Systems Consultant
www.paragonit.com.au
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Saikovski
Sent: Thursday, 14 February 2008 4:19 PM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] Weird SQL error
of that would help the automation of this
process. Anyone know of such?
Thanks
Greg Mulholland
--- OzMOSS.com
- to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject.
Powered
-1d1339f2435f1033.mspx?mfr=true
Cheers,
Daniel
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Greg Mulholland
Sent: Thursday, 7 February 2008 11:46 AM
To: listserver@ozMOSS.com
Subject: [OzMOSS] Documenting MOSS 2007
Hi There All
Ive been asked
I recently had a problem with a web app that i managed to fix by extending
it to another IIS site, the orginal still doesnt work but the new does.
The issue i have now is that the site,port and host header are now
different are now site2 port 81 instead of the orignal site1 port 80.
I have yet to
I recently had a problem with a web app that i managed to fix by extending
it to another IIS site, the orginal still doesnt work but the new does.
The issue i have now is that the site,port and host header are now
different are now site2 port 81 instead of the orignal site1 port 80.
I have yet to
