Shared Windows Calendar across home network

Hi all, Vista Ultimate SP2 32 Bit

I would like to know if it is possible to subscribe to a shared Windows Calendar on one machine by all my machines across my home network by subscribing to the one Calendar .ICS.

I have shared the Windows calendar on the one machine and published the calendar to a folder on my Data drive that is accessible to all machines via the home network. The other drives on the same machine can access the calendar by subscribing to it. But, when I tried to subscribe to that ics file from one of the other machines via the home network it does not work. It can access the folder and file, but, it will not subscribe to it when I enter it into the subscription line.

What do I need to do to be able to share this published calendar by all the machines. They each have the same version of Vista installed.

Any suggestions would be very much appreciated.

Jan

A couple of (untested) ideas ...

You could perhaps set up a web server on the main machine, with the
networked computers accessing it.like a web address, or another possibility
might be replacing the 'Calendars' folder on each of the networked computers
at

%localappdata%\Microsoft\Windows Calendar\Calendars

with a 'junction' to the location of the .ics file on the machine containing
the 'Data' drive.


--
Jon

"The great fights of the world are all fought in the mind" (John Buchan)


"Jan " <> wrote in message
news:...
Hi all, Vista Ultimate SP2 32 Bit

I would like to know if it is possible to subscribe to a shared Windows
Calendar on one machine by all my machines across my home network by
subscribing to the one Calendar .ICS.

I have shared the Windows calendar on the one machine and published the
calendar to a folder on my Data drive that is accessible to all machines via
the home network. The other drives on the same machine can access the
calendar by subscribing to it. But, when I tried to subscribe to that ics
file from one of the other machines via the home network it does not work.
It can access the folder and file, but, it will not subscribe to it when I
enter it into the subscription line.

What do I need to do to be able to share this published calendar by all the
machines. They each have the same version of Vista installed.

Any suggestions would be very much appreciated.

Jan

Hi Jon..thanks for the suggestion. Not sure what you mean by a 'junction'.
Would you mind to elaborate on that a bit for me. It sounds interesting.
As each machine has a Windows Calendar I thought that perhaps subscribing to
the primary published calendar would work, but, not sure I have it set up
correctly. I've never shared, published or subscribed with a Windows
Calendar before so I may have missed something along the way. But, I'm open
to other ideas as well.

Jan



"Jon" <> wrote in message
news:%...
>A couple of (untested) ideas ...
>
> You could perhaps set up a web server on the main machine, with the
> networked computers accessing it.like a web address, or another
> possibility might be replacing the 'Calendars' folder on each of the
> networked computers at
>
> %localappdata%\Microsoft\Windows Calendar\Calendars
>
> with a 'junction' to the location of the .ics file on the machine
> containing the 'Data' drive.
>
>
> --
> Jon
>
> "The great fights of the world are all fought in the mind" (John Buchan)
>
>
> "Jan " <> wrote in message
> news:...
> Hi all, Vista Ultimate SP2 32 Bit
>
> I would like to know if it is possible to subscribe to a shared Windows
> Calendar on one machine by all my machines across my home network by
> subscribing to the one Calendar .ICS.
>
> I have shared the Windows calendar on the one machine and published the
> calendar to a folder on my Data drive that is accessible to all machines
> via the home network. The other drives on the same machine can access the
> calendar by subscribing to it. But, when I tried to subscribe to that ics
> file from one of the other machines via the home network it does not work.
> It can access the folder and file, but, it will not subscribe to it when I
> enter it into the subscription line.
>
> What do I need to do to be able to share this published calendar by all
> the machines. They each have the same version of Vista installed.
>
> Any suggestions would be very much appreciated.
>
> Jan

"Jan " <> wrote in message
news:%...
> Hi Jon..thanks for the suggestion. Not sure what you mean by a
> 'junction'. Would you mind to elaborate on that a bit for me. It sounds
> interesting. As each machine has a Windows Calendar I thought that perhaps
> subscribing to the primary published calendar would work, but, not sure I
> have it set up correctly. I've never shared, published or subscribed with
> a Windows Calendar before so I may have missed something along the way.
> But, I'm open to other ideas as well.
>


Here's a Wikipedia article that explains what a junction is (it's
essentially a folder shortcut that behaves as it it were the destination
folder itself),...

NTFS junction point
http://en.wikipedia.org/wiki/NTFS_junction_point

....but having just read the article it would appear that junctions aren't
supported for directories on remote shares. So it probably wouldn't work.

One way that should work, it to have a (startup) script on the networked
machines that copies the .ics file from the networked 'Data' drive
(+perhaps other relevant files from %localappdata%\Microsoft\Windows
Calendar\Calendars ) to the

%localappdata%\Microsoft\Windows Calendar\Calendars

folder on each networked machine, with Calendar on each networked machine
subscribed to the local version.

But there may well be simpler ways that you'll discover, or that others can
suggest.

--
Jon

Thanks, Jon, I'll take a look at the information and try your other
suggestion and see what happens.

I truly appreciate your time and help. :-)

Jan

"Jon" <> wrote in message
news:...
> "Jan " <> wrote in message
> news:%...
>> Hi Jon..thanks for the suggestion. Not sure what you mean by a
>> 'junction'. Would you mind to elaborate on that a bit for me. It sounds
>> interesting. As each machine has a Windows Calendar I thought that
>> perhaps subscribing to the primary published calendar would work, but,
>> not sure I have it set up correctly. I've never shared, published or
>> subscribed with a Windows Calendar before so I may have missed something
>> along the way. But, I'm open to other ideas as well.
>>
>
>
> Here's a Wikipedia article that explains what a junction is (it's
> essentially a folder shortcut that behaves as it it were the destination
> folder itself),...
>
> NTFS junction point
> http://en.wikipedia.org/wiki/NTFS_junction_point
>
> ...but having just read the article it would appear that junctions aren't
> supported for directories on remote shares. So it probably wouldn't work.
>
> One way that should work, it to have a (startup) script on the networked
> machines that copies the .ics file from the networked 'Data' drive
> (+perhaps other relevant files from %localappdata%\Microsoft\Windows
> Calendar\Calendars ) to the
>
> %localappdata%\Microsoft\Windows Calendar\Calendars
>
> folder on each networked machine, with Calendar on each networked machine
> subscribed to the local version.
>
> But there may well be simpler ways that you'll discover, or that others
> can suggest.
>
> --
> Jon
>
>
>

I can get the calendars on the same machine subscribed to the one folder ok,
but, not via the network.

Here's my thoughts...take one Windows calendar on my primary machine and
publish it to a specific folder on the data hard drive (no OS installed)
that is accessible by all machines via the network. Set the Publish to
automatic so that any new information or edits would be automatically
updated. Then have the Windows calendars from the other machines subscribe
to that folder and published ics, and make them able to add or edit and then
automatically publish to that ics in that folder on the primary machine so
that I could add or update/edit from any machine and the primary calendar
would be updated. I would think that, according to the Publish instructions
it can be published to a web folder or a folder on a hard drive. If it is
accessible on a web folder by all machines to subscribe to, then why would
it not be accessible in the same token from a network hard drive folder.
But, so far that does not seem to be possible, as I can't seem to subscribe
to the folder from another machine. Even when it has the same name, such as
<username> Calendar.ics. If they can make it accessible for more than one
machine from the web folder, why can it not be accessible by more than one
machine from a local home network drive?

Jan


"Jon" <> wrote in message
news:...
> "Jan " <> wrote in message
> news:%...
>> Hi Jon..thanks for the suggestion. Not sure what you mean by a
>> 'junction'. Would you mind to elaborate on that a bit for me. It sounds
>> interesting. As each machine has a Windows Calendar I thought that
>> perhaps subscribing to the primary published calendar would work, but,
>> not sure I have it set up correctly. I've never shared, published or
>> subscribed with a Windows Calendar before so I may have missed something
>> along the way. But, I'm open to other ideas as well.
>>
>
>
> Here's a Wikipedia article that explains what a junction is (it's
> essentially a folder shortcut that behaves as it it were the destination
> folder itself),...
>
> NTFS junction point
> http://en.wikipedia.org/wiki/NTFS_junction_point
>
> ...but having just read the article it would appear that junctions aren't
> supported for directories on remote shares. So it probably wouldn't work.
>
> One way that should work, it to have a (startup) script on the networked
> machines that copies the .ics file from the networked 'Data' drive
> (+perhaps other relevant files from %localappdata%\Microsoft\Windows
> Calendar\Calendars ) to the
>
> %localappdata%\Microsoft\Windows Calendar\Calendars
>
> folder on each networked machine, with Calendar on each networked machine
> subscribed to the local version.
>
> But there may well be simpler ways that you'll discover, or that others
> can suggest.
>
> --
> Jon
>
>
>

"Jan " <> wrote in message
news:%23PYcF$...
>I can get the calendars on the same machine subscribed to the one folder
>ok, but, not via the network.
>
> Here's my thoughts...take one Windows calendar on my primary machine and
> publish it to a specific folder on the data hard drive (no OS installed)
> that is accessible by all machines via the network. Set the Publish to
> automatic so that any new information or edits would be automatically
> updated. Then have the Windows calendars from the other machines
> subscribe to that folder and published ics, and make them able to add or
> edit and then automatically publish to that ics in that folder on the
> primary machine so that I could add or update/edit from any machine and
> the primary calendar would be updated. I would think that, according to
> the Publish instructions it can be published to a web folder or a folder
> on a hard drive. If it is accessible on a web folder by all machines to
> subscribe to, then why would it not be accessible in the same token from a
> network hard drive folder. But, so far that does not seem to be possible,
> as I can't seem to subscribe to the folder from another machine. Even
> when it has the same name, such as <username> Calendar.ics. If they can
> make it accessible for more than one machine from the web folder, why can
> it not be accessible by more than one machine from a local home network
> drive?
>
> Jan



I don't have any further ideas, sorry (perhaps someone else will). It's a
complicated issue to resolve via a newsgroup. It's the sort of thing that
really requires an hands-on approach, with a lot of trial and error to see
what actually works. But I wish you well, and if you do manage to come up
with a solution then let us know.

--
Jon

Thanks, Jon. :-)

Jan

"Jon" <> wrote in message
news:...
> "Jan " <> wrote in message
> news:%23PYcF$...
>>I can get the calendars on the same machine subscribed to the one folder
>>ok, but, not via the network.
>>
>> Here's my thoughts...take one Windows calendar on my primary machine and
>> publish it to a specific folder on the data hard drive (no OS installed)
>> that is accessible by all machines via the network. Set the Publish to
>> automatic so that any new information or edits would be automatically
>> updated. Then have the Windows calendars from the other machines
>> subscribe to that folder and published ics, and make them able to add or
>> edit and then automatically publish to that ics in that folder on the
>> primary machine so that I could add or update/edit from any machine and
>> the primary calendar would be updated. I would think that, according to
>> the Publish instructions it can be published to a web folder or a folder
>> on a hard drive. If it is accessible on a web folder by all machines to
>> subscribe to, then why would it not be accessible in the same token from
>> a network hard drive folder. But, so far that does not seem to be
>> possible, as I can't seem to subscribe to the folder from another
>> machine. Even when it has the same name, such as <username>
>> Calendar.ics. If they can make it accessible for more than one machine
>> from the web folder, why can it not be accessible by more than one
>> machine from a local home network drive?
>>
>> Jan
>
>
>
> I don't have any further ideas, sorry (perhaps someone else will). It's a
> complicated issue to resolve via a newsgroup. It's the sort of thing that
> really requires an hands-on approach, with a lot of trial and error to see
> what actually works. But I wish you well, and if you do manage to come up
> with a solution then let us know.
>
> --
> Jon
>
>
>