Thread: dot net 3.5
View Single Post
  #13  
Old October 5th 17, 05:16 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default dot net 3.5

VanguardLH wrote:
T wrote:

I haven't found anything that has Cobian's feature set
to replace it. You have any suggestions? It must have zero
proprietary formats and backups must be readable by any
file manager, including non-windows file managers. And it
must eMail reports. VSS compatibility is a requirement.


We've been through this before. Those are YOUR requirements, not the
customer's. Their limitations in choice seem more you limitation.

None of the free backup programs that I've tried are lacking VSS
support. All have an e-mail report option (you can select to report on
success, failure, or just one of those - so failure reports is what is
really needed). However, most would require you buy them to the e-mail
report feature yet, as I said, they're paying you so I don't believe
that having to pay $30-$40 per workstation is outside their budget.

Hope the other info about .Net 3.5 helped. Did you check if it was
already installed? As winston hinted, maybe you have to enable it
(i.e., the files would already have to be available or installable
internally) as a Windows feature? If it is already there then another
install might have it step atop of whatever corruption you think there
may be with it.

I've also found advice about getting .Net 3.5 to work in Windows 10 by
running:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess
/Source:drive:\sources\sxs

drive, uppercased, is whatever is the drive letter for the install
media with the ISO of Windows 10. I think the capitals are important in
this command but if the command fails then try all lowercase.


I got the impression part of what T does with
Cobian, is scripting. Not all backup programs are that
good at scripting.

*******

https://www.veritas.com/support/en_US/article.000037440

vssadmin list providers

Symantec Software VSS Provider
Microsoft Software Shadow Copy provider 1.0

vssadmin list writers

State: Stable
No error

It could be that commands like that, might show an entry
for Outlook, and the scheme used to make the Outlook
data store quiescent when a backup runs. Maybe it's
the Outlook code (an older version of Outlook) that
is looking for .net 3.5 and CLR 2.0.

Paul
Ads