Thanks @michele_sas   We upgraded from M5 to M7 a couple of years ago. I see from our order summary that .Net 4.8 was supplied with M7, and I think it would have been .Net 4.6 with M5. That would explain why the other three servers have 4.8 installed (I don't remember that bit in the upgrade but, as I say, it was two years ago and I had someone from SAS UK doing it with me). I don't quite understand why it didn't install for the mid-tier server though - maybe just wasn't a requirement for the mid-tier software, which doesn't include SAS Foundation?    I have already raised a track with TS just to confirm. ... View more

I would imagine that software developed on any platform will make use of native libraries. My thoughts were that in Windows these would be based on the .Net Framework because in effect the whole of Windows is. But, I'm not a software developer so I can't really comment authoritatively.  ... View more

I'd be very surprised if that was the case. The Dot Net Framework is built in to Windows these days, but doesn't appear as an installed program. I think if you checked the registry here HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full you'd find entries indicating the version which is installed. This page tells you how to determine the actual version: https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed  Nearly all Windows software is built on Dot Net, so I can't imagine that SAS for Windows wasn't. Not including the Java bits, of course. But I would expect Java for Windows itself was built on Dot Net. ... View more

It's horses for courses really! Using native SAS tables is likely to be more efficient just because there's  nothing in between SAS and the data. But it depends what your data sources are. We have quite a few in separate databases (SQL Server/Oracle/PostgreSQL) but most users extract from them and save the results locally for analysis. This has the added advantage that, as the sources are operational databases, the source of a specific analysis is always available as a snapshot of the data. Having said that, our analysts are moving towards having a separate platform for hosting all their analytical data, using SQL Server and Sharepoint. This has metadata built in to its front end, so that it is searchable on different topics. It means the analysts aren't restricted to any single analytical tool. SAS is the main one but we have an increasing number of R users, and there have always been a few people who prefer other platforms such as SPSS, Stata and so on. It's also become quite important because there are a wide range of areas for analysis (eg. health, education, transport, justice), which sometimes have cross-overs between them. ... View more

Thanks, you could be right. I'd always assumed the record option only worked with install/uninstall/hotfixes but I've been able to create response files for rebuilds and redeployments. It contains sasadm credentials (with an encoded password) and specifies the web apps as metadata object IDs. So I reckon they should actually work. Will have to have a wee think about it. Not something to do at a whim. ... View more

I'm glad it's useful.   As you say, Get-Process is quite limiting. Get-WmiObject is useful for getting the owner, parent and command line, although having identified how to do this last one I don't think I actually use it. I should really think about replacing Get-WmiObject with the newer Get-CimInstance but sometimes life's too short, and it works! I use a SAS program to join this data with parsed object spawner logs and data from our business directory database. This gives me data sets with full organisational information which I can use for monitoring purposes and also for recharging our licence costs. Nobody else uses it! But given that the results of the Powershell are in the CSV files, other tools could be used for processing them fairly easily (not as nicely as SAS, I would contend 😉). Have to say, I love Powershell! I was brought kicking and screaming from a Solaris environment when it was decided to move our SAS servers to Windows about 10 years ago. I'd been scratching my head trying to work out how to replace a whole load of shell scripts with Windows .bat files (not possible!) But then someone suggested I look at Powershell and the rest, as they say, is history. ... View more

You can either use Enterprise Guide to connect to the Linux SAS server, rather than a full SAS Windowing environment, or use an X Server package to run SAS on the Linux machine. ... View more

Here's a Powershell script (need to take the .txt extension off for that we use to monitor SAS sessions on our Windows server. It creates a CSV file with a list of user ID, PID, start time, CPU (total and user) and command line. It's scheduled to run every 15 minutes and then we have SAS programs to process the files once a day. Years ago when we were on Solaris we had a shell script which did a similar thing. ... View more

We upgraded straight from M5 to M7 (Windows servers but don't see why it would be different for any other OS). We did it with help from a specialist from SAS though. ... View more

Thanks Greg. TS are taking a look. I'll report back. ... View more