Re: w32tm.exe Help Understanding-Resolved

[Ben Scott]

On Thu, Dec 22, 2011 at 6:27 PM, Heaton, Joseph@DFG  wrote:
> Which is why we have leap years every 4 years J

  Except when the year is divisible by 100.

  Except when the year is divisible by 400.  Then it's a leap year again.

  And don't even ask about September 1752.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: w32tm.exe Help Understanding-Resolved

[Heaton, Joseph@DFG]

Which is why we have leap years every 4 years :)

From: John Bonner [mailto:johnbon...@centura.org]
Sent: Thursday, December 22, 2011 3:17 PM
To: Heaton, Joseph@DFG; NT System Admin Issues
Subject: w32tm.exe Help Understanding-Resolved

And for the second one I need to use 365.242199 days in a year. Over 300 years 
that fraction adds up.

DOH!

Well have a blessed Christmas and thanks for all your help during the year.

JB

From: Bonner, John
Sent: Thursday, December 22, 2011 3:57 PM
To: 'NT System Admin Issues'
Subject: w32tm.exe Help Understanding

Hello and Merry Christmas,

I am feeling pretty dumb here and would like to wrap up one of my projects 
before the holiday

Currently I am trying to do some calculations using w32tm.exe to validate my 
math...and my math appears to be wrong.
For example I Google how many nanoseconds in a day. From multiple sources I get 
86,400,000,000,000. Fine then w32tm.exe should match saying 1 daybut it 
doesn't  It says 100 days

C:\Users\jbonner>w32tm.exe /ntte 864000
100 00:00:00.000 - 4/10/1601 5:00:00 PM

A day is a day regardless so I can't see that time zone would matter for this 
simple calculation??

So let's say Google is wrong and I use 864,000,000,000 which does show as one 
day.

C:\Users\jbonner>w32tm.exe /ntte 8640
1 00:00:00.000 - 4/10/1601 5:00:00 PM

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of nanoseconds till 
1-1-1901. That would be

300 (1901-1601)
365 (days in a year)
300 * 365 = 109,500 days

109500 days * 8640 (nanoseconds in a day) = 94,608,000,000,000,000

Close but no dice.

C:\Users\jbonner>w32tm.exe /ntte 94608
109500 00:00:00.000 - 10/20/1900 5:00:00 PM

So I am pretty confused and any clarification would be greatly appreciated.
JB

*
This communication is for the use of the intended recipient only. It may
contain information that is privileged and confidential. If you are not the
intended recipient of this communication, any disclosure, copying, further
distribution or use thereof is prohibited. If you have received this
communication in error, please advise me by return e-mail or by telephone and
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: w32tm.exe Help Understanding--Update

[Michael B. Smith]

A year contains (more-or-less, but more accurately than what you've specified) 
365.25 days (a leap-year happens each four years, but not ALWAYS every four 
years).

300 * 365.25 = 109,575

109,575 * (24 * 60 * 60 * 10,000,000) = 94,672,800,000,000,000

C:\> W32tm /ntte 946728000
109575 00:00:00.000 - 1/3/1901 7:00:00 PM

Using PowerShell to perform these types of date calculations is a LOT easier 
than attempting to do it manually, as well as less prone to error (it knows all 
of the proper adjustments to make).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Bonner, John [mailto:johnbon...@centura.org]
Sent: Thursday, December 22, 2011 6:13 PM
To: NT System Admin Issues
Subject: w32tm.exe Help Understanding--Update

OK I figured out the first one. It is not the number of naonoseconds. It is 100 
nanosecond intervals. So that makes sense as for the 100 days when it should be 
one day.
Still working on the second one.


Hello and Merry Christmas,

I am feeling pretty dumb here and would like to wrap up one of my projects 
before the holiday.

Currently I am trying to do some calculations using w32tm.exe to validate my 
math...and my math appears to be wrong.
For example I Google how many nanoseconds in a day. From multiple sources I get 
86,400,000,000,000. Fine then w32tm.exe should match saying 1 daybut it 
doesn't  It says 100 days

C:\Users\jbonner>w32tm.exe /ntte 864000
100 00:00:00.000 - 4/10/1601 5:00:00 PM

A day is a day regardless so I can't see that time zone would matter for this 
simple calculation??

So let's say Google is wrong and I use 864,000,000,000 which does show as one 
day.

C:\Users\jbonner>w32tm.exe /ntte 8640
1 00:00:00.000 - 4/10/1601 5:00:00 PM

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of nanoseconds till 
1-1-1901. That would be

300 (1901-1601)
365 (days in a year)
300 * 365 = 109,500 days

109500 days * 8640 (nanoseconds in a day) = 94,608,000,000,000,000

Close but no dice.

C:\Users\jbonner>w32tm.exe /ntte 94608
109500 00:00:00.000 - 10/20/1900 5:00:00 PM

So I am pretty confused and any clarification would be greatly appreciated.
JB


*
This communication is for the use of the intended recipient only. It may
contain information that is privileged and confidential. If you are not the
intended recipient of this communication, any disclosure, copying, further
distribution or use thereof is prohibited. If you have received this
communication in error, please advise me by return e-mail or by telephone and
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

w32tm.exe Help Understanding-Resolved

[Bonner, John]

And for the second one I need to use 365.242199 days in a year. Over 300
years that fraction adds up. 

 

DOH!

 

Well have a blessed Christmas and thanks for all your help during the
year.

 

JB

 

From: Bonner, John 
Sent: Thursday, December 22, 2011 3:57 PM
To: 'NT System Admin Issues'
Subject: w32tm.exe Help Understanding

 

Hello and Merry Christmas,

 

I am feeling pretty dumb here and would like to wrap up one of my
projects before the holiday.

 

Currently I am trying to do some calculations using w32tm.exe to
validate my math...and my math appears to be wrong.

For example I Google how many nanoseconds in a day. From multiple
sources I get 86,400,000,000,000. Fine then w32tm.exe should match
saying 1 daybut it doesn't  It says 100 days

 

C:\Users\jbonner>w32tm.exe /ntte 864000

100 00:00:00.000 - 4/10/1601 5:00:00 PM

 

A day is a day regardless so I can't see that time zone would matter for
this simple calculation??

 

So let's say Google is wrong and I use 864,000,000,000 which does show
as one day. 

 

C:\Users\jbonner>w32tm.exe /ntte 8640

1 00:00:00.000 - 4/10/1601 5:00:00 PM

 

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of
nanoseconds till 1-1-1901. That would be

 

300 (1901-1601)

365 (days in a year)

300 * 365 = 109,500 days

 

109500 days * 8640 (nanoseconds in a day) =
94,608,000,000,000,000

 

Close but no dice.

 

C:\Users\jbonner>w32tm.exe /ntte 94608

109500 00:00:00.000 - 10/20/1900 5:00:00 PM

 

So I am pretty confused and any clarification would be greatly
appreciated.

JB

 

*
This communication is for the use of the intended recipient only.  It may 
contain information that is privileged and confidential.  If you are not the 
intended recipient of this communication, any disclosure, copying, further 
distribution or use thereof is prohibited.  If you have received this 
communication in error, please advise me by return e-mail or by telephone and 
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: w32tm.exe Help Understanding

[Michael B. Smith]

W32tm.exe doesn't use nanoseconds, it uses 0.1 microseconds.

w32tm /ntte 
  Convert a NT system time, in (10^-7)s intervals from 0h 1-Jan 1601,
  into a readable format.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Bonner, John [mailto:johnbon...@centura.org]
Sent: Thursday, December 22, 2011 5:57 PM
To: NT System Admin Issues
Subject: w32tm.exe Help Understanding

Hello and Merry Christmas,

I am feeling pretty dumb here and would like to wrap up one of my projects 
before the holiday.

Currently I am trying to do some calculations using w32tm.exe to validate my 
math...and my math appears to be wrong.
For example I Google how many nanoseconds in a day. From multiple sources I get 
86,400,000,000,000. Fine then w32tm.exe should match saying 1 daybut it 
doesn't  It says 100 days

C:\Users\jbonner>w32tm.exe /ntte 864000
100 00:00:00.000 - 4/10/1601 5:00:00 PM

A day is a day regardless so I can't see that time zone would matter for this 
simple calculation??

So let's say Google is wrong and I use 864,000,000,000 which does show as one 
day.

C:\Users\jbonner>w32tm.exe /ntte 8640
1 00:00:00.000 - 4/10/1601 5:00:00 PM

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of nanoseconds till 
1-1-1901. That would be

300 (1901-1601)
365 (days in a year)
300 * 365 = 109,500 days

109500 days * 8640 (nanoseconds in a day) = 94,608,000,000,000,000

Close but no dice.

C:\Users\jbonner>w32tm.exe /ntte 94608
109500 00:00:00.000 - 10/20/1900 5:00:00 PM

So I am pretty confused and any clarification would be greatly appreciated.
JB

*
This communication is for the use of the intended recipient only. It may
contain information that is privileged and confidential. If you are not the
intended recipient of this communication, any disclosure, copying, further
distribution or use thereof is prohibited. If you have received this
communication in error, please advise me by return e-mail or by telephone and
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

w32tm.exe Help Understanding--Update

[Bonner, John]

OK I figured out the first one. It is not the number of naonoseconds. It
is 100 nanosecond intervals. So that makes sense as for the 100 days
when it should be one day.

Still working on the second one.

 

 

Hello and Merry Christmas,

 

I am feeling pretty dumb here and would like to wrap up one of my
projects before the holiday.

 

Currently I am trying to do some calculations using w32tm.exe to
validate my math...and my math appears to be wrong.

For example I Google how many nanoseconds in a day. From multiple
sources I get 86,400,000,000,000. Fine then w32tm.exe should match
saying 1 daybut it doesn't  It says 100 days

 

C:\Users\jbonner>w32tm.exe /ntte 864000

100 00:00:00.000 - 4/10/1601 5:00:00 PM

 

A day is a day regardless so I can't see that time zone would matter for
this simple calculation??

 

So let's say Google is wrong and I use 864,000,000,000 which does show
as one day. 

 

C:\Users\jbonner>w32tm.exe /ntte 8640

1 00:00:00.000 - 4/10/1601 5:00:00 PM

 

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of
nanoseconds till 1-1-1901. That would be

 

300 (1901-1601)

365 (days in a year)

300 * 365 = 109,500 days

 

109500 days * 8640 (nanoseconds in a day) =
94,608,000,000,000,000

 

Close but no dice.

 

C:\Users\jbonner>w32tm.exe /ntte 94608

109500 00:00:00.000 - 10/20/1900 5:00:00 PM

 

So I am pretty confused and any clarification would be greatly
appreciated.

JB

 

 

*
This communication is for the use of the intended recipient only.  It may 
contain information that is privileged and confidential.  If you are not the 
intended recipient of this communication, any disclosure, copying, further 
distribution or use thereof is prohibited.  If you have received this 
communication in error, please advise me by return e-mail or by telephone and 
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

w32tm.exe Help Understanding

[Bonner, John]

Hello and Merry Christmas,

 

I am feeling pretty dumb here and would like to wrap up one of my
projects before the holiday.

 

Currently I am trying to do some calculations using w32tm.exe to
validate my math...and my math appears to be wrong.

For example I Google how many nanoseconds in a day. From multiple
sources I get 86,400,000,000,000. Fine then w32tm.exe should match
saying 1 daybut it doesn't  It says 100 days

 

C:\Users\jbonner>w32tm.exe /ntte 864000

100 00:00:00.000 - 4/10/1601 5:00:00 PM

 

A day is a day regardless so I can't see that time zone would matter for
this simple calculation??

 

So let's say Google is wrong and I use 864,000,000,000 which does show
as one day. 

 

C:\Users\jbonner>w32tm.exe /ntte 8640

1 00:00:00.000 - 4/10/1601 5:00:00 PM

 

Fine w32tm.exe has an epoch of 1-1-1601. I want the number of
nanoseconds till 1-1-1901. That would be

 

300 (1901-1601)

365 (days in a year)

300 * 365 = 109,500 days

 

109500 days * 8640 (nanoseconds in a day) =
94,608,000,000,000,000

 

Close but no dice.

 

C:\Users\jbonner>w32tm.exe /ntte 94608

109500 00:00:00.000 - 10/20/1900 5:00:00 PM

 

So I am pretty confused and any clarification would be greatly
appreciated.

JB

 

*
This communication is for the use of the intended recipient only.  It may 
contain information that is privileged and confidential.  If you are not the 
intended recipient of this communication, any disclosure, copying, further 
distribution or use thereof is prohibited.  If you have received this 
communication in error, please advise me by return e-mail or by telephone and 
delete/destroy it.
*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Interesting Windows 8 logon feature

[Andrew S. Baker]

I just clean my screen regularly. :)

* *

*ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of
Technology for the SMB market…

*



On Tue, Dec 20, 2011 at 5:53 PM, Crawford, Scott wrote:

>  I like it. Of course, you could implement this feature now on your own.**
> **
>
> ** **
>
> *From:* Andrew S. Baker [mailto:asbz...@gmail.com]
> *Sent:* Tuesday, December 20, 2011 3:36 PM
>
> *To:* NT System Admin Issues
> *Subject:* Re: Interesting Windows 8 logon feature
>
> ** **
>
> After you've traced the correct password, the cursor should move in a
> random path for 5 seconds, and you should have to follow it before
> completely logging on.   :)
> 
>
> *ASB*
>
> *http://XeeMe.com/AndrewBaker*
>
> *Harnessing the Advantages of Technology for the SMB market…*
>
>
>
> 
>
> On Tue, Dec 20, 2011 at 4:14 PM, Jonathan Link 
> wrote:
>
> I don't disagree with that.  I also don't see it happening anytime soon,
> or any way of ensuring that this feature is only used on smudge resistant
> screens.
>
> ** **
>
> On Tue, Dec 20, 2011 at 4:04 PM, Andrew S. Baker 
> wrote:
>
> It's actually a good idea, but we need to see more development of
> smudge-resistant screens...
> 
>
> *ASB*
>
> *http://XeeMe.com/AndrewBaker*
>
> *Harnessing the Advantages of Technology for the SMB market…*
>
>
>
> 
>
> On Tue, Dec 20, 2011 at 3:47 PM, Jonathan Link 
> wrote:
>
> Sure, but if you're making a consisent motion to authenticate, whether it
> is in different locations or one location it will likely stand out enough.
> If it's in different locations you can better sort out the common elements
> to making the motion.
>
>  
>
> This just seems ill-advised.  ** **
>
> On Tue, Dec 20, 2011 at 2:45 PM, Joseph Heaton  wrote:
> 
>
>   Well, the screen’s going to be smudged from normal usage anyway.  Not
> sure how they’d be able to figure out which smudges were for what.
>
>  
>
> *From:* Mike Hoffman [mailto:m...@drumbrae.net]
> *Sent:* Tuesday, December 20, 2011 11:34 AM
> *To:* Joseph Heaton; NT System Admin Issues
> *Subject:* RE: Interesting Windows 8 logon feature
>
>  
>
> It’s enabled in the Preview build – and it’s so much easier than typing a
> password. I used a family photo for a while and the password was to draw a
> noose round the mother-in-law’s head – what fun.
>
>  
>
> What would be good is if they could move the photo around that way you
> don’t get smudge marks in the same place.
>
>  
>
> Mike
>
>  
>
> *From:* Steven Peck [mailto:sep...@gmail.com]
> *Sent:* 20 December 2011 18:39
> *To:* NT System Admin Issues
> *Subject:* Re: Interesting Windows 8 logon feature
>
>  
>
> This was demo'd in the Build videos if you want to see a demo of it. 
>
>  
>
>
>  
>
> On Tue, Dec 20, 2011 at 10:29 AM, James Rankin 
> wrote:
>
> http://www.bbc.co.uk/news/technology-16247659
>
>  
>
>
> 
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: IIS 4.0 and .docx MIME types

[Ben Scott]

On Thu, Dec 22, 2011 at 3:26 PM, Blasko, Margo 
wrote:
> This is an intranet site that I don't manage - not sure what you mean
> about 'What HTTP headers is the web server offering when you HEAD
> the URL'.

  HEAD is one of the HTTP commands ("methods").  It gets headers without
retrieving the content.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4

  By examining the HTTP headers, we can get an idea of what the server is
doing/thinking.

  From a Linux shell:

$ *telnet www.purple.com 80*
Trying 153.104.63.227...
Connected to www.purple.com (153.104.63.227).
Escape character is '^]'.
*HEAD /purple.html HTTP/1.1
Host: purple.purple.com

*HTTP/1.1 200 OK
Date: Thu, 22 Dec 2011 20:40:48 GMT
Server: Unknown
Last-Modified: Sat, 26 Nov 2011 18:14:47 GMT
ETag: "46e94-299-3ea313c0"
Accept-Ranges: bytes
Content-Length: 665
Content-Type: text/html; charset=ISO-8859-1

*^]*
telnet> *quit*
Connection closed.
$

  Stuff I sent (typed) is in bold green.^] represents +<]>.  One
has to type the blank line after the "Host:" header to signify the end of
the client request to the server.

  I'm using Linux here because the Telnet client works better than
Microsoft's.  You can use the one that comes with Windows, but it doesn't
handle raw TCP connections well.  In particular, it doesn't echo what you
type, so you have to type blind.  You could also use any other terminal
client that supports raw TCP connections.  PuTTY does.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~

~ ;  ~



---

To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/

or send an email to listmana...@lyris.sunbeltsoftware.com

with the body: unsubscribe ntsysadmin

Re: IIS 4.0 and .docx MIME types

[Jeff Bunting]

Sounds like IIS is successfully serving the file if Word is complaining
about the format.  Could the document be from a different (prob. older)
version of word?  Rather than opening, can you save the file locally and
try extension as .doc and see if Word will open.

Jeff

On Thu, Dec 22, 2011 at 2:35 PM, Blasko, Margo
wrote:

> All,
>
> Entered
> application/vnd.openxmlformats-officedocument.wordprocessingml.document as
> the .docx MIME type in ISS 4.0 on a Windows 2000 server.   The server was
> then rebooted.
>
> Unfortuantely the docx documents still will not open.  The error is 'Word
> cannot open the file because the file format does not match the file
> extension'
>
> Is this a compatibility issue?  Can I get .docx to work on IIS4.0? Or
> could there be something else?
>
> Thanks in advance,
>
> Margo
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: IIS 4.0 and .docx MIME types

[Ben Scott]

On Thu, Dec 22, 2011 at 2:35 PM, Blasko, Margo
 wrote:
> Entered 
> application/vnd.openxmlformats-officedocument.wordprocessingml.document as 
> the .docx MIME type in ISS 4.0 on a Windows 2000 server.   The server was 
> then rebooted.
>
> Unfortuantely the docx documents still will not open.

  Serving up documents and opening files are two different things.

  What HTTP headers is the web server offering when you HEAD the URL?

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: IIS 4.0 and .docx MIME types

[Damien Solodow]

I think I see your problem... Windows 2000 should be IIS5. ;)

DAMIEN SOLODOW
Systems Engineer
317.447.6033 (office)
317.447.6014 (fax)
HARRISON COLLEGE

From: Erik Goldoff [mailto:egold...@gmail.com]
Sent: Thursday, December 22, 2011 2:51 PM
To: NT System Admin Issues
Subject: Re: IIS 4.0 and .docx MIME types

Win 2000 and IIS 4 ??? ouch !

How could docx not be compatible with an end of life'd unsupported system ? 




On Thu, Dec 22, 2011 at 2:35 PM, Blasko, Margo 
mailto:margo.bla...@dcc-cdc.gc.ca>> wrote:
All,

Entered application/vnd.openxmlformats-officedocument.wordprocessingml.document 
as the .docx MIME type in ISS 4.0 on a Windows 2000 server.   The server was 
then rebooted.

Unfortuantely the docx documents still will not open.  The error is 'Word 
cannot open the file because the file format does not match the file extension'

Is this a compatibility issue?  Can I get .docx to work on IIS4.0? Or could 
there be something else?

Thanks in advance,

Margo
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: IIS 4.0 and .docx MIME types

[Erik Goldoff]

Win 2000 and IIS 4 ??? ouch !

How could docx not be compatible with an end of life'd unsupported system ?




On Thu, Dec 22, 2011 at 2:35 PM, Blasko, Margo
wrote:

> All,
>
> Entered
> application/vnd.openxmlformats-officedocument.wordprocessingml.document as
> the .docx MIME type in ISS 4.0 on a Windows 2000 server.   The server was
> then rebooted.
>
> Unfortuantely the docx documents still will not open.  The error is 'Word
> cannot open the file because the file format does not match the file
> extension'
>
> Is this a compatibility issue?  Can I get .docx to work on IIS4.0? Or
> could there be something else?
>
> Thanks in advance,
>
> Margo
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

IIS 6 redirects

[Joseph L. Casale]

I have a website bound to port 81 & 443 with some redirects.

One vdir has a single redirect, another has two, then there is 4th I am unsure 
about.

Is there a programmatic way to enumerate the redirects in a clear way, and can 
I just drop a redirect by clearing out the associated start and end tags for 
the redirect?

I assume unless enabling direct metabase edits I will have to restart iis?

Thanks guys,
jlc

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Federation?

[Brian Desmond]

More of an application question and what federation tooling you'll use. ADFS 
from Microsoft is free and reasonably straight forward to setup. The work is in 
each application integration. Some are easy, some aren't.

Thanks,
Brian Desmond
br...@briandesmond.com

w - 312.625.1438 | c   - 312.731.3132

From: David Lum [mailto:david@nwea.org]
Sent: Thursday, December 22, 2011 11:32 AM
To: NT System Admin Issues
Subject: Federation?

How hard is it to enable federation with Active Directory?  2003 AD schema.
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 503.267.9764



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Federation?

[David Lum]

How hard is it to enable federation with Active Directory?  2003 AD schema.
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 503.267.9764



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin