fordea

Could it possibly be the Edge shortcut that Windows 10 creates on user's desktops? We've disabled this via GPO: Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer Value: DisableEdgeDesktopShortcutCreation Data: 1 Type: REG_DWORD

We had the same issue, turns out the March rollup Windows update broke something with WDS: https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881. It seems to work again after applying the suggested fix in that article to disable the "Enable Variable Window Extension" setting on the WDS server. Not the best timing with this as I imagine a fair amount of us will be imaging over Easter holidays!

I think the main benefits of Office 365 for schools are what it provides in addition to email for no cost: Pros: Users get 1TB of OneDrive storage each Web versions of the office suite which provide nice collaboration functionality Students can install the Office suite on up to five of their personal devices thanks to the student advantage program (you'll need to ask your Office reseller about how to do this) You may also be able to get the above for staff depending on your current Office licensing agreement You may be able to use device based activation to install Office 365 CTR at your school depending on your current Office licensing agreement. There's some good threads on Edugeek about setting this up Office 365 provides free email-encryption (requires a bit of setup) Access to SharePoint to create an intranet Since the GDPR has come in to effect Microsoft have made great advances in the data protection side of things. They've added lots of functionality to the Security & Compliance center within Office365 to help protect your organisations data. Having Office 365 logins for your students/staff opens up the potential for single-sign-on capabilities to a host of online services. Can enable two-factor authentication for your Office 365 logins Cons: Office 365 uptime/availability is generally good but there's been a number of blips recently. Trying to explain to staff that there's nothing you can do to fix an issue and that it's in Microsoft's hands is always fun Not really a con in my book but certain things on the management side of Office 365 require some PowerShell knowledge which can be a bit daunting at first. Becomes extremely powerful though when you get to grips with it If I can think of any more I'll add them in!

You can change the initial $result assignment to include a calculated property for csname in Select-Object: [color=#333333]$result = Get-WmiObject win32_operatingsystem -ComputerName $ComputerName | select @{LABEL='PC Name';EXPRESSION={$_.csname}}, @{LABEL='LastBootUpTime';EXPRESSION={$_.ConverttoDateTime($_.lastbootuptime)}} [/color][/Code]

Try add the following lines below where you use Add-Member to add the IP Address to $result: $Date = Get-Date $Result | Add-Member -MemberType NoteProperty -Name Date -Value ($Date.ToString('dd/MM/yyyy')) $Result | Add-Member -MemberType NoteProperty -Name Time -Value ($Date.ToString('HH:mm:ss')) [/Code]

So you probably don't have WinRM enabled in your environment which is why my code isn't working for you. The simplest way to modify your code would be by making use of your $result1 variable and using the Add-Member cmdlet: [system.Reflection.Assembly]::LoadWithPartialName('Microsoft.VisualBasic') | Out-Null $ComputerName = [Microsoft.VisualBasic.Interaction]::InputBox("Enter computer name", "ComputerName", "$env:ComputerName") $result = Get-WmiObject win32_operatingsystem -ComputerName $ComputerName | select csname, @{LABEL='LastBootUpTime';EXPRESSION={$_.ConverttoDateTime($_.lastbootuptime)}} $result1 = (Get-WmiObject -Class Win32_NetworkAdapterConfiguration -ComputerName $ComputerName -Filter 'ipenabled = "true"').IPAddress $result | Add-Member -MemberType NoteProperty -Name 'IP Address' -Value $result1 [system.Windows.Forms.MessageBox]::Show("$result") [system.Windows.Forms.MessageBox]::Show("Saved to Log file on D:") $result | Export-Csv "D:\RebootPcLog.csv" -Append -NoTypeInformation [/Code] If the above code ends up with 'System.Object' entries in your IP Address column in the csv then it's because your query to Win32_NetworkAdapterConfiguration is returning multiple IP addresses (probably an IPv4 and IPv6 address). If you only want the IPv4 address then you can modify the $result1 line: [Code] $result1 = ((Get-WmiObject -Class Win32_NetworkAdapterConfiguration -ComputerName $ComputerName -Filter 'ipenabled = "true"').IPAddress | Where {$_ -notlike '*:*'}) -join ';' [/Code]

If you've copied my code you'll need to do as howartp suggests and declare a $ComputerName variable as I forgot put that in. If you want to keep the method you've used to ask for a computer name you could just add these two lines above my code: [color=#333333][system.Reflection.Assembly]::LoadWithPartialName('Microsoft.VisualBasic') | Out-Null[/color] [color=#333333]$ComputerName = [Microsoft.VisualBasic.Interaction]::InputBox("Enter computer name", "ComputerName", "$env:ComputerName") [/color][/Code][color=#333333] If you've already declared a $ComputerName variable then you may be getting a blank csv if the computer name is unreachable. If that still doesn't work then you might be using an older version of PowerShell. You can type $PSVersionTable into a PowerShell window to see what version you're using.[/color]

In that case something like this should do the trick: $Results = Invoke-Command -ComputerName $ComputerName -ErrorAction SilentlyContinue -ScriptBlock { $OSInfo = Get-CimInstance -ClassName Win32_OperatingSystem $IPInfo = Get-CimInstance -ClassName Win32_NetworkAdapterConfiguration -Filter 'ipenabled = "true"' $Date = Get-Date [PSCustomObject] @{ Date = $Date.ToString('dd/MM/yyyy') Time = $Date.ToString('HH:mm:ss') Name = $env:computername IPAddress = $IPInfo.IPAddress | Where {$_ -notlike '*:*'} LastBootTime = $OSInfo.LastBootUpTime } } $Results | Select-Object * -ExcludeProperty RunspaceID, PSComputerName | Export-Csv D:\RebootPcLog.csv -NoTypeInformation -Append [/Code]

This should be fairly straightforward to do. May I ask what the overall goal of the script is as it would be quicker/simpler to have Powershell retrieve host IP address/lease information from your DHCP server?

Is the DHCP server still authorized in AD?

You've got the right idea. You'll have to import your csv data using the Import-Csv cmdlet, loop through all the rows adding your additional column data and then finally output that to a new/existing csv file using the Export-Csv cmdlet. If you let me know what code you've got so far I can give you a hand with this or you can alter the template below to suit your needs: $inputData = Import-Csv -Path 'C:\input.csv' foreach ($row in $inputData) { $LastLogonTimeStamp = #code here that retrieves the lastlogontimestamp for this particular row $row | Add-Member -MemberType NoteProperty -Name 'LastLogonTimeStamp' -Value $LastLogonTimeStamp -Force } $inputData | Export-Csv -Path 'C:\output.csv' -NoTypeInformation[/Code]

From that description it sounds like a visual bug. Probably a long shot but have you tried to disable hardware acceleration in the Office suite to see if that helps? Should find it under File -> Options -> Advanced -> Display Section -> Disable hardware graphics acceleration.

It looks like the Word Mailmerge option for SIMS reports generates a Reportmailmerge.csv file in MyDocuments/tempSimsRpt with the data. Have you checked that this csv file is correct and isn't missing the values? Also may be worth trying to copy that generated csv file and manually adding it as a merge source in Word to see if you still get the same issue.

Have you tried adding a dummy row in Excel just below the column headers that contains 255+ characters in each cell where that column is giving you blanks in the merge?

Not sure if this could be it but it looks like your *.exe exception '%appdata%\local\microsoft\onedrive\' should actually be '%localappdata%\microsoft\onedrive\'. I think %appdata% goes to the roaming folder in the profile

Right I think we're getting somewhere with this. Found a thread from last year that describes our problem exactly and has a solution: http://www.edugeek.net/forums/windows-10/190793-1709-smb1-issue-only-1-server.html Basically it looks like our server running SIMS has had the SMB2/3 driver startup type set to disabled at some point in the past (no idea why). You can see if this is the case on your server by checking the SMBClient Operational log. We saw the following event each time the server was booted: The SMB 3 and SMB 2 driver is not configured with the default start type. Default Start Type: DEMAND_START Configured Start Type: DISABLED The proposed fix is to set the start type back to auto by running the following two commands and then rebooting the server: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc.exe config mrxsmb20 start= auto I'm still waiting for a suitable time to reboot but I'm pretty confident that this will resolve the issue. *EDIT: Just confirming this has worked for us after a reboot, SIMS server can now browse to 1803 admin shares and can deploy the agent to them. We didn't event need to turn on File and Printer sharing in 1803 but we do have the firewall ports configured for this in Group Policy.

I'm glad to hear that SOLUS works with SMB2 as I didn't really want to enable SMB1 on our 1803 clients. I tried to enable the file and print sharing as I noticed it's disabled by default on 1803 but no luck. I'll have to troubleshoot this further as it only seems to be our SIMS server that can't access the C$ share of 1803 clients so it's probably a server-side setting.

We are having this issue with new builds of Windows 10 1709 and 1803 and we think it's because Microsoft has disabled SMB1 by default on these builds. Once we turned the SMB1 client and server features on for the workstations we could then browse to their C$ shares from our SIMS server and subsequently deploy SIMS via Solus to them. It's really odd because every other server we've tried was able to access these clients via the admin shares prior to enabling SMB1 support, just not on our SIMS server.

I recommend checking this article out as it will show you an implementation of logon/logoff scripts by using Powershell and will also populate multiple log files based on user, computer and date: https://www.jasonpearce.com/2016/12/26/use-powershell-to-log-logon-and-logoff-activity-on-domain-computers/ In terms of adding an additional column for the IPv4 addresses into the script(s) in the article above you could add something like this before the lines containing 'Export-CSV' cmdlets: $IPAddresses = (Get-CimInstance -ClassName Win32_NetworkAdapterConfiguration | Where-Object {$_.IPAddress} | Select-Object -ExpandProperty IPAddress | Where-Object {$_ -notlike '*:*'}) -join ', ' $obj | Add-Member -MemberType NoteProperty -Name 'IPAddress' -Value $IPAddresses

Not sure if these are widely known about but Greenshot and Sharex are great screenshot applications that have helped me numerous times when creating user guides or sending some instructions over in an email.