Jump to content


radish

Established Members
  • Content Count

    61
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by radish

  1. AlwaysOn server multi-instance, 2 member servers W2019-SCCMDB1\MSSQLSERVER 1433,4022 W2019-SCCMDB1\MSSQLSERVER2 1633,4023 W2019-SCCMDB2\MSSQLSERVER 1433,4022 W2019-SCCMDB2\MSSQLSERVER2 1633,4023 AlwayOn-DB 192.168.160.122 5022 5044 port AlwayOn-DB2 192.168.160.123 5023 5045 port First migrate the management center site to W2019-SCCMDB1\MSSQLSERVER2. Everything is fine, even if the members of the alwayson database are restarted. After the management center site completes the restoration of active replication status, I am migrating the main site database to W2019-SCCMDB1\MSSQLSERVER. If the AlwaysOn database member server is restarted at this time, this situation will reappear, and I discovered this problem when I shut down the failover. Once the AlwaysOn database member server is restarted, the management center site must fail to connect, and the SQL cannot be connected. It seems that it is caused by the SQL certificate problem? If you clear the certificate in the sql configuration tool, the MSSQLSERVER2 instance can be connected, but then the CAS console cannot be connected. Don't know what is going on here? At present, the W2019-SCCMDB2 server has been restarted and the SQL connection login failure occurs. W2019-SCCMDB1 can still be used normally because it has not been restarted. Whether SCCM cannot host the SCCM site database in the AlwaysON environment with multiple instances, this problem will surely recur. I don’t know how to check the problem. Is it the SCCM certificate problem or the SQL AlwaysON problem? It is guessed that it is caused by the SQL certificate. Since the main site was the last to migrate, the SQL certificate generated by the main site will invalidate the SQL certificate generated by the previous management center site?
  2. Need to write a script to achieve, when there is an old system, it should be installed on the old system partition Here is a video tutorial to install to the original system disk location without formatting other partitions, but it seems to be a paid video https://edu.51cto.com/center/course/lesson/index?id=567096
  3. Yes, 66 and 67 must be set to see the actual situation of the device When the number of VLANs is relatively small or when the switch setting does not support ip helper, You can set a distribution point for each vlan to solve the OSD problem.
  4. Make sure that the hard disk partitions are checked. This partition is set as the boot partition. In the SCCM OSD, only bios is recognized as the first boot method of a certain hard disk. Otherwise, an error will occur in the application operating system and the WIM image package cannot be released If there are two hard disks, disk number 0 HDD and disk number 1 SSD, you need to install the operating system to the SSD, pay attention! ! ! The bios sets the HDD hard disk as the first boot hard disk first. Then in the task sequence step, the disk 1 partition step must be set as the boot partition, which prevents IT technicians from manually adjusting the bios settings, which is suitable for automated OSD. The traditional MBR boot method to install the operating system is affected by this, UEFI is not affected by this rule. See if it is caused by this problem.
  5. Agree with this view, system computer account installation and user installation of some software will cause installation errors
  6. Then use the script to detect that there is no dependent software installed
  7. Yes, click this link to check the conditions after the upgrade I reset the main site server two or three times, and even tried modify sql server configuration and modify SMSProvider configuration. I also reset the management center site, and it remains the same. I have been trying for two days and have not found an effective solution to this problem.
  8. After sccm2002 server Windows2012R2 is upgraded to server2019, The specified server is not a configuration manager site server A management center site 666 is windows2019, and a main site 888 was originally Windows2012R2 upgraded to Windows2019 Added in the registry Software\Microsoft\SMS HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths The sms permission in wmi is also eligible After upgrading the operating system as required, the main site was reset Does anyone know what's going on? The specified server is not a configuration manager site server How to check the log to fix this problem? I am glad that this problem is solved, I run the installation file from the backup file Reinstall the site server It is now back to normal. This is the step required to clean up the existing server Clean an existing server for site server recovery only Delete SMS registry keys: HKLM\Software\Microsoft\SMS Delete any registry entries starting with SMS from HKLM\System\CurrentControlSet\Services. For example: SMS_DISCOVERY_DATA_MANAGER SMS_EXECUTIVE SMS_INBOX_MONITOR SMS_INVENTORY_DATA_LOADER SMS_LAN_SENDER SMS_MP_FILE_DISPATCH_MANAGER SMS_SCHEDULER SMS_SITE_BACKUP SMS_SITE_COMPONENT_MANAGER SMS_SITE_SQL_BACKUP SMS_SITE_VSS_WRITER SMS_SOFTWARE_METERING_PROCESSOR SMS_STATE_SYSTEM SMS_STATUS_MANAGER SMS_WSUS_SYNC_MANAGER SMSvcHost 3.0.0.0 SMSvcHost 4.0.0.0 Uninstall the Configuration Manager console Restart the server Confirm that all of the above registry keys are deleted. The server is now ready for the Configuration Manager restore procedure.
  9. Hi friends I encountered a problem. I set up a secondary site in the subdomain to enable PXE distribution points, and the client failed to start after PXE startup. The prompt reply has no message header marker, Failed to send status message (80004005) I have tried to update the certificate, delete the pxe settings, delete the secondary site server, and reinstall the operating system. It still works. What should I do? Can anyone help how to change the log to deal with this failure Finally use the new computer name of the secondary site server Reinstall the secondary site to use the new secondary site code ad subdomain secondary site server client pxe started and resumed normal use Reference https://social.technet.microsoft.com/Forums/en-US/019cb2a2-e412-4e1e-b790-413005a20631/secondary-site-cannot-get-sql-certificate-from-parent?forum=configmanagerdeployment SMSPXE.log
  10. How can MDT UDI obtain this volume information, such as F:\windows(54GB) is the disk number 1 It seems that I did not find the variable disk number name stored in this volume in the MDT variable name I want to do gui through here to select disk information to format and install the system completely Choose 1 disk number hard disk, format or start formatting from 0 number. Suppose the user selects F:\windows(54GB) disk number 1 on the udi interface, and OSDDiskIndex is updated to the corresponding disk number selected instead of starting from the default disk number 0 The key point is that this udi choice depends on the user, so I can't specify a fixed disk number to update the OSDDiskIndex value, I wonder if there is any way to achieve this for MDT UDI? 请问 MDT UDI 如何获取这个 volume 信息,如 F:\windows(54GB)是磁盘编号1 貌似我在MDT变量名称没找到这个volume 所存储的变量磁盘编号名称 我想通过这里来做gui来选择磁盘信息进行格式化并全新安装系统 选择1磁盘编号硬盘,格式化还是从0编号开始格式化。 假设用户在udi界面 选择 F:\windows(54GB)磁盘编号为1,OSDDiskIndex就更新为所选择对应磁盘编号,而不是从默认磁盘编号0开始 重点在于这个udi选择取决与用户 所以我无法指定固定磁盘编号来更新OSDDiskIndex值,不知道 MDT UDI 这个有没什么方法可以实现吗?
  11. Although this is very old post information, but recently I just researched this kind of multi-disk installation operating system on the hard disk with a disk number other than 0 to solve this problem. The first type: is to set the model of disk number 1 in the bios as the first boot disk, The second type: Just keep the boot sequence set in the partition 0 task sequence. When the OSD reaches the disk number 1, the boot file will be written to the partition 0. Solve the prompt message when applying the operating system Failed to make volume 😧 \ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. The request is not supported. (Error: 80070032; Source: Windows)
  12. This can be solved by taking the folder name $a.split('\')[2] -replace '\.\w+$' google $a.Substring(0,$f.LastIndexOf('.')).split('\')[2] google
  13. $a = "C:\Program Files (x86)\Google\Chrome\Application\80.0.3987.149\Installer\setup.exe --uninstall --system-level --verbose-logging" $a -replace '([^\\]*)$' Suppose my condition is like this How do I extract the desired folder name $b = $a -replace '([^\\]*)$' $b = google or $b =chrome or $b = Application
  14. I have a copy item copy script running the output log under windows platform to _SMSTSLogPath. The output log cannot be set successfully. I tried to fail. What should I do? $start = Get-Date Function Import-SMSTSENV{ $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment $TSEnv.Value("_SMSTSLogPath") # Create an object to access the task sequence environment #$tsenv = New-Object -ComObject Microsoft.SMS.TSEnvironment # Query the environment to get an existing variable # Set a variable for the task sequence log path $LogPath = $tsenv.Value("_SMSTSLogPath") } #创建日志文件名称 $detetetime = (get-date -format "yyyy年MM月dd日HH时MM分ss秒") $applicationlog = "$detetetime" + "HD Tune Pro v5.70 v2 免注册汉化版单文件.log" $applicationlog #启动powershell控制台日志记录 Start-transcript -path $LogPath\"$applicationlog" #Start-transcript -path $env:temp\"$applicationlog" #<# #> #当前目录 #$scriptPath = split-path -parent $MyInvocation.MyCommand.Definition #获取脚本运行所在目录 $executingScriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent #判断操作系统32位以及64位的Program Files目录Program Files (x86),并根据操作系统位数输出目录 $application = (${env:ProgramFiles(x86)}, ${env:ProgramFiles} -ne $null)[0] #变量赋值自定义文件夹如:在"Program Files 或 (Program Files x86)" 路径里创建一个 "HD Tune Pro v5.70 v2 免注册汉化版单文件" 文件夹 $application2 = "HD Tune Pro v5.70 v2 免注册汉化版单文件" #变量赋值自定义快捷方式桌面快捷方式名称如:HDTunePro_Win8_10 $lnkshortcutname = "HDTunePro_Win8_10" #变量赋值自定义原始程序名称如:HDTunePro_Win8_10.exe $lnkshortcutname2 = "HDTunePro_Win8_10.exe" #变量赋值自定义文件夹路径如:C:\Program Files\HD Tune Pro v5.70 v2 免注册汉化版单文件 $newapplication = "$application\$application2" #变量赋值自定义快捷方式桌面路径如:C:\Program Files\HD Tune Pro v5.70 v2\HDTunePro_Win8_10.exe $lnknewapplication = "$application\$application2\$lnkshortcutname2" #判断文件夹名是否存在并创建文件夹 if(-not (Test-Path $newapplication)){ mkdir "$newapplication" | Out-file $env:temp"\"'$applicationlog' } #判断powershell运行x86 x64版本 $newPSVersion = if ([IntPtr]::Size -eq 8){ 'x64' } else { 'x86' } #查询时间 $datetime = get-date -format "yyyy年MM月dd日HH:MM:ss" #当前区域语言 $LANG = (Get-Culture).Name #查询操作系统名称以及位数 $ws = (Get-WmiObject Win32_OperatingSystem).osarchitecture $OS = (Get-WmiObject -Class Win32_OperatingSystem).Caption #查询IP相关信息 $wmi = Get-WmiObject win32_networkadapterconfiguration -filter "ipenabled = 'true'" $ipwgdef = $wmi.DefaultIPGateway $ipdizhi = (ipconfig|select-string "IPv4"|out-string).Split(":")[-1].trim() -replace(" |`t|\r|\`n ,``") $ipyanma = (ipconfig|select-string "子网掩码"|out-string).Split(":")[-1].trim() -replace(" |`t|\r|\`n ,``") #$ARCHITECTURE = $env:PROCESSOR_ARCHITECTURE #获取PS脚本文件名 $ScriptName = $MyInvocation.MyCommand.Name #系统信息输出显示powershell窗口 Write-Output "" Write-Output "$ScriptName - 当前时间:$datetime" Write-Output "$ScriptName - 用 户名: $env:USERNAME" Write-Output "$ScriptName - 计算机名: $env:COMPUTERNAME" Write-Output "$ScriptName - IP 地址: $ipdizhi" Write-Output "$ScriptName - 网 关: $ipwgdef" Write-Output "$ScriptName - IP 掩码: $ipyanma" Write-Output "$ScriptName - 当前域名: $env:USERDNSDOMAIN" Write-Output "$ScriptName - 源 路径: $executingScriptDirectory" Write-Output "$ScriptName - 目的路径:$newapplication" Write-Output "$ScriptName - 操作系统: $OS $ws " Write-Output "$ScriptName - 当前语言: $LANG " Write-Output "$ScriptName - PSVersion:$newPSVersion $($PSVersionTable.PSVersion.tostring())" #开始复制文件,并排除复制指定Copy20200315.ps1脚本文件 Get-ChildItem -Path "$executingScriptDirectory" -Exclude "*.ps1" | Copy-Item -Recurse -Destination "$newapplication" #(Get-ChildItem -Path "$executingScriptDirectory" -Exclude "*.ps1" | Copy-Item -Recurse -Destination "$newapplication" -verbose 4>&1).Message #开始创建快捷键图标步骤 $shortcut_name = "$lnkshortcutname" #快捷键图标名称 $shortcut_target = "$lnknewapplication" #设置快捷键桌面图标路径 $sh = new-object -com "WScript.Shell" $p = $sh.SpecialFolders.item("AllUsersDesktop") #设置到 All\Users\Desktop\ 桌面路径 $lnk = $sh.CreateShortcut( (join-path $p $shortcut_name) + ".lnk" ) $lnk.TargetPath = $shortcut_target $lnk.IconLocation = "$lnknewapplication" #设置快捷键桌面图标ICO $lnk.Save() $end = Get-Date #脚本总运行时间 Write-Host ('Total Runtime: ' + ($end - $start).TotalSeconds)秒 Start-Sleep -s 60 #停止powershell控制台日志 Stop-transcript
  15. Hi friend, I do n’t see the icon option when I open Orca software. Why is this?
  16. I remember this error was some system patches released in March or May last year, updated and then caused this error. Later, a fix patch released by Microsoft around October resolved the sccm pxe boot error. In addition, does the boot integrate the VMXNET3 network card driver? The TFTP accelerated startup mode is modified to try to adjust parameters according to the respective corporate network environment.
  17. Thank you very much for anyweb. I tried to write a simple ps script to execute the exe to solve the software center status failure problem. I am sorry that I still have a bad command of the powershell script. Please tell me how to hide the powershell window. PS:\#Start-Process .\DingTalk_v4.7.29.19.exe -NoNewWindow -Wait
  18. I know that it is possible to distribute and repackage software by application (after all, repackaging software is also a laborious task. Not all system administrators know how to operate repackaging software, especially some complex installation packages) Solve the successful installation of this software and customize the detection of successful installation conditions. What I want to know is when distributing software through packages, is there any way to solve it, or is there any way to set the corresponding attributes when the software is released by the package? When the system detects this information, it means that the installation has been successful. For example, although this dingtalk installation was successful, the returned result is a 1223 code causing the software center status to indicate that the installation failed. You can fill in the corresponding information attribute values through the attribute information here, such as General or Reporting, such as comparing the information generated from the software installation and registration to indicate the conditions for successful installation, or how to customize the MIF file yourself. I have been puzzled for a long time. How to solve this problem when using software to distribute software? The software has been successfully installed. The software center status is detected as a failure indicator. Can anyone help? Thank you very much.
  19. Support for the Application Catalog role has ended since version 1910 Since version 1806 Specify the visibility of the Application Catalog website link on the Installation Status tab in the Software Center. For more information, see Software Center Client Settings. You no longer need the Application Catalog role to display the applications available to users in Software Center. This change helps reduce the server infrastructure required to deliver applications to users. Software Center now relies on management points to get this information, helping them scale better by assigning larger environments to boundary groups Refer to the official Microsoft documentation
  20. About automatic computer naming when SCCM deploys computers I have a powershell script that is used to automatically name the computer when the OS is deployed. But when a known computer is deployed, skip this based on task variables or how to satisfy the name of a known computer Script execution. Name is win7x64-test 101 About automatic computer naming when SCCM deploys computers I have a Powershell script for automatically naming computers when OS is deployed. However, when deploying a known computer, depending on the task variable or how the name of the known computer is satisfied, the script will be skipped and not executed. For example, the known computer name is win7x64-test101
  21. Yes, I know win7 will stop updating, I'm testing. This is my calculation name named script. How to use conditional skip script execution when the computer is known to be deployed on the OS, use this ps script to automatically name the computer only if the computer is unknown
  22. Yes, I know win7 will stop updating, I'm testing. This is my calculation name named script. In the case where the OS deployment computer is known, if you use conditions to skip this script execution, use this ps script to automatically name the computer only if the computer is unknown
  23. 关于SCCM部署计算机时候自动计算机命名问题 我有个powershell脚本是用来自动部署OS时给计算机自动命名规则的, 但是在已知计算机部署时,根据任务变量或如何满足已知计算机的名字跳过这个不 脚本执行。的名字为win7x64-测试101 关于SCCM部署计算机时的自动计算机命名 我有一个Powershell脚本,用于在部署OS时自动命名计算机。 但是,在部署已知计算机时,根据任务变量或如何满足已知计算机的名称,将跳过该脚本并不执行此脚本。 例如,已知的计算机名称是win7x64-test101 About automatic computer naming when SCCM deploys computers I have a powershell script that is used to automatically name the computer when the OS is deployed. But when a known computer is deployed, skip this based on task variables or how to satisfy the name of a known computer Script execution. Name is win7x64-test 101 About automatic computer naming when SCCM deploys computers I have a Powershell script for automatically naming computers when OS is deployed. However, when deploying a known computer, depending on the task variable or how the name of the known computer is satisfied, the script will be skipped and not executed. For example, the known computer name is win7x64-test101 客户端GUID = GUID:50026e2f-8972-4596-bd14-6b395b710c89,Netbios名称= WIN7X64-TEST101,状态=已知 TL TIME OSDComputerName.ps1 win7x64.zip smsts.log
×
×
  • Create New...